How do I install the Analyzing Source Project skill?

Run npx skillmds@latest add qte77-claude-code-utils/analyzing-source-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Analyzing Source Project safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Analyzing Source Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Analyzing Source Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Analyzing Source Project?

qte77 (@qte77-claude-code-utils) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Analyzing Source Project by qte77-claude-code-utils

Name: Analyzing Source Project
Rating: 4.2 (5 reviews)
Author: qte77

File contents

Analyzing Source Project (Phase 0)

Target: $ARGUMENTS

Phase 0 of the GTM pipeline. Produces a technical capability profile of the source project that feeds Phase 1B (researching-market).

Mode Awareness

Read config/mode.md before starting:

concise — Bullet summaries, 3-5 points per section
detailed — Full narrative with evidence and code references
conservative — Focus on proven, documented capabilities
ambitious — Highlight unrealized potential and extension opportunities

Inputs

config/sources.md — Source projects to analyze
config/comments_research.md — Research constraints and focus areas
config/mode.md — Style and approach settings

Workflow

Identify source projects from config/sources.md
Clone or fetch the repository if a URL is provided (use WebFetch for public repos)
Assess architecture — Directory structure, module boundaries, design patterns
Inventory tech stack — Languages, frameworks, dependencies, infrastructure hints
Extract differentiators — What does this project do unusually well?
Identify limitations — Scalability ceilings, missing features, tech debt signals
Rate capabilities — Score each capability area (1-5) with rationale
Validate against criteria — Check config/validation_criteria.md Phase 0 gates

Output

Write to results/phase-0/:

`capability-profile.md`

# Source Project Capability Profile

## Project: [name]

## Architecture Summary
[Overview of system design and key components]

## Tech Stack
- Language: [language + version]
- Framework: [framework]
- Key dependencies: [list]

## Differentiating Capabilities
1. [Capability] — Score: [1-5] — Evidence: [file/feature reference]
2. ...

## Limitations and Risks
- [Limitation] — Impact: [High/Medium/Low]

## GTM-Relevant Technical Signals
[How technical characteristics translate to market positioning opportunities]

Rules

Ground every capability claim in observable code or documentation evidence
Distinguish between current state and aspirational/roadmap features
Limitations are as important as strengths for honest PMF assessment
Cross-reference with config/comments_research.md scope constraints

---name: analyzing-source-projectdescription: Assess a source project's technical capabilities. Reads `config/sources.md` and produces a structured capability profile. Use to start the GTM pipeline or evaluate technical differentiators (Phase 0).---# Analyzing Source Project (Phase 0)**Target**: $ARGUMENTSPhase 0 of the GTM pipeline. Produces a technical capability profile of thesource project that feeds Phase 1B (researching-market).## Mode AwarenessRead `config/mode.md` before starting:- `concise` — Bullet summaries, 3-5 points per section- `detailed` — Full narrative with evidence and code references- `conservative` — Focus on proven, documented capabilities- `ambitious` — Highlight unrealized potential and extension opportunities## Inputs- `config/sources.md` — Source projects to analyze- `config/comments_research.md` — Research constraints and focus areas- `config/mode.md` — Style and approach settings## Workflow1. **Identify source projects** from `config/sources.md`2. **Clone or fetch** the repository if a URL is provided (use WebFetch for public repos)3. **Assess architecture** — Directory structure, module boundaries, design patterns4. **Inventory tech stack** — Languages, frameworks, dependencies, infrastructure hints5. **Extract differentiators** — What does this project do unusually well?6. **Identify limitations** — Scalability ceilings, missing features, tech debt signals7. **Rate capabilities** — Score each capability area (1-5) with rationale8. **Validate against criteria** — Check `config/validation_criteria.md` Phase 0 gates## OutputWrite to `results/phase-0/`:### `capability-profile.md````# Source Project Capability Profile## Project: [name]## Architecture Summary[Overview of system design and key components]## Tech Stack- Language: [language + version]- Framework: [framework]- Key dependencies: [list]## Differentiating Capabilities1. [Capability] — Score: [1-5] — Evidence: [file/feature reference]2. ...## Limitations and Risks- [Limitation] — Impact: [High/Medium/Low]## GTM-Relevant Technical Signals[How technical characteristics translate to market positioning opportunities]```## Rules- Ground every capability claim in observable code or documentation evidence- Distinguish between current state and aspirational/roadmap features- Limitations are as important as strengths for honest PMF assessment- Cross-reference with `config/comments_research.md` scope constraints

Frequently asked questions

Analyzing Source Project