What is analyzing-source-project?

A workflow for assessing what a software project can do by examining its source, configuration, architecture, technologies, strengths, and limitations. It produces a structured capability profile for later market analysis.

Use it to review source projects, inventory their technology and modules, identify differentiators and limits, and prepare input for go-to-market research.

Planning a product or launch without understanding the underlying project can lead to unsupported claims and poor decisions. This workflow gathers technical evidence first.

analyzing-source-project — Skill by qte77

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/qte77/claude-code-plugins/analyzing-source-project

Any agent

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

Clone the repo

git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 613 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00044	$0.00613
Opus 5	$0.00022	$0.00307
Sonnet 5	$0.00009	$0.00123
Haiku 4.5	$0.00004	$0.00061

Measured yesterday against content hash 5e92cfcb7b8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyzing-source-project scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/market-research/skills/analyzing-source-project/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 79 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 79 lines · 44 tokens per session scan A 5e92cfcb7b8a

Subscribe to this mod's changes

analyzing-source-project is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 613 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Data and AI Research agent-skills ai-coding-tools claude-code claude-code-marketplace claude-code-plugins claude-code-skills

orchestrator

FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.

aleksandr-chaika/flutter-clean-arch-skills · 72 tokens

flutter-guide

Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.

aleksandr-chaika/flutter-clean-arch-skills · 39 tokens

maestro-flutter

Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.

aleksandr-chaika/flutter-clean-arch-skills · 41 tokens

android-kotlin-compose

Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…

and3r817/dot-claude-plugins · 84 tokens

android-kotlin-coroutines

Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…

and3r817/dot-claude-plugins · 87 tokens

codex-advisor

Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…

and3r817/dot-claude-plugins · 85 tokens