Skf analyze source
Skill armelhbobdad/oh-my-skills/.claude/skills/skf-analyze-source
Discover what to skill in a large repo and produce recommended skill briefs. Use when the user requests to "analyze source for skills" or "discover skill opportunities."From its SKILL.md
npx -y skills add armelhbobdad/oh-my-skills --skill skf-analyze-sourceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 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.
SKILL.md
3.1 KB, 734 tokens by cl100k_base, as published. Nobody here has run it
Analyze Source
Overview
Analyzes a large repo or multi-service project to identify discrete skillable units, map exports and integration points, and produce recommended skill-brief.yaml files as the primary entry point for brownfield onboarding. The analysis must be thorough enough to produce actionable briefs, but scoped enough to avoid overwhelming the user with false positives. Scanning depth adapts to forge tier — Quick (file structure), Forge (AST), Forge+ (AST + CCC semantic pre-ranking), Deep (AST+QMD).
Role
You are a source code analyst and decomposition architect collaborating with a developer onboarding an existing project. You bring expertise in codebase analysis, service boundary detection, and skill scoping, while the user brings their domain knowledge. Work together as equals.
Workflow Rules
These rules apply to every step in this workflow:
- Read each step file completely before taking any action
- Follow the mandatory sequence in each step exactly — do not skip, reorder, or optimize
- Only load one step file at a time — never preload future steps
- Update
stepsCompletedin output file frontmatter before loading next step - If any instruction references a subprocess or tool you lack, achieve the outcome in your main context thread
- Always communicate in
{communication_language} - If
{headless_mode}is true, auto-proceed through confirmation gates with their default action and log each auto-decision
Stages
| # | Step | File | Auto-proceed |
|---|---|---|---|
| 1 | Initialize | steps-c/step-01-init.md | Yes |
| 1b | Continue (session resume) | steps-c/step-01b-continue.md | Yes |
| 2 | Scan Project | steps-c/step-02-scan-project.md | No (confirm) |
| 3 | Identify Units | steps-c/step-03-identify-units.md | No (confirm) |
| 4 | Map & Detect | steps-c/step-04-map-and-detect.md | Yes |
| 5 | Recommend | steps-c/step-05-recommend.md | No (confirm) |
| 6 | Generate Briefs | steps-c/step-06-generate-briefs.md | Yes |
| 7 | Workflow Health Check | steps-c/step-07-health-check.md | Yes |
Invocation Contract
| Aspect | Detail |
|---|---|
| Inputs | project_path [required], scope_hint [optional] |
| Gates | step-02: Confirm Gate [C] |
| Outputs | analysis-report.md, skill-brief.yaml files (one per recommended unit) |
| Headless | All gates auto-resolve with default action when {headless_mode} is true |
On Activation
-
Load config from
{project-root}/_bmad/skf/config.yamland resolve:project_name,output_folder,user_name,communication_language,document_output_language,forge_data_folder,skills_output_folder,sidecar_path
-
Resolve
{headless_mode}: true if--headlessor-Hwas passed as an argument, or ifheadless_mode: truein preferences.yaml. Default: false. -
Load, read the full file, and then execute
./steps-c/step-01-init.mdto begin the workflow.
What ships with it: 11 files
58.9 KB alongside SKILL.md
assets/
- skill-brief-schema.md10.5 KB
references/
steps-c/
- step-01b-continue.md2.5 KB
- step-01-init.md4.8 KB
- step-02-scan-project.md5.5 KB
- step-03-identify-units.md4.9 KB
- step-04-map-and-detect.md8.0 KB
- step-05-recommend.md6.2 KB
- step-06-generate-briefs.md7.4 KB
- step-07-health-check.md806 B
templates/
Gives 0 of the 12 instructions most research analysis skills give in 734 tokens
Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07
- Generate a markdown reportin 32 of 1063, across 23 files
- Cite each claim's sourcein 30 of 1063, across 15 files
- Define the ideal customer profilein 20 of 1063, across 2 files
- Search for companies matching the criteriain 20 of 1063, across 2 files
- Assign a fit score from one to tenin 20 of 1063, across 2 files
- Analyze the codebase to understand the productin 19 of 1063, across 1 file
- Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
- Look for signals of immediate needin 19 of 1063, across 1 file
- Identify the target decision maker rolein 19 of 1063, across 1 file
- Suggest a personalized contact strategyin 19 of 1063, across 1 file
- Provide conversation starters for outreachin 19 of 1063, across 1 file
- Format results in a scannable markdown templatein 19 of 1063, across 1 file
Said here and by no other author read
- load one step file at a time
- communicate in the configured communication language
- auto-proceed through confirmation gates in headless mode
- load config on activation
- Read each step file completely before taking action
- Follow the mandatory sequence exactly without skipping or reordering
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.