agentsclimarketplace

Analyzing source project

Skill qte77/claude-code-plugins/plugins/market-research/skills/analyzing-source-project

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install
npx -y skills add qte77/claude-code-plugins --skill analyzing-source-project

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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).

SKILL.md

2.7 KB, as published. Nobody here has run it

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

  1. 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 patterns
  4. Inventory tech stack — Languages, frameworks, dependencies, infrastructure hints
  5. Extract differentiators — What does this project do unusually well?
  6. Identify limitations — Scalability ceilings, missing features, tech debt signals
  7. Rate capabilities — Score each capability area (1-5) with rationale
  8. 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.