agentsclimarketplace

Skf analyze source

Skill armelhbobdad/oh-my-skills/_bmad/skf/skf-analyze-source

Curated collection of agentskills.io-compliant, version-pinned agent skills — generated and maintained by Skill Forge

Install
npx -y skills add armelhbobdad/oh-my-skills --skill skf-analyze-source

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

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

What its author says it does

Copied from the file, not written here

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

SKILL.md

3.1 KB, 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 stepsCompleted in 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

#StepFileAuto-proceed
1Initializesteps-c/step-01-init.mdYes
1bContinue (session resume)steps-c/step-01b-continue.mdYes
2Scan Projectsteps-c/step-02-scan-project.mdNo (confirm)
3Identify Unitssteps-c/step-03-identify-units.mdNo (confirm)
4Map & Detectsteps-c/step-04-map-and-detect.mdYes
5Recommendsteps-c/step-05-recommend.mdNo (confirm)
6Generate Briefssteps-c/step-06-generate-briefs.mdYes
7Workflow Health Checksteps-c/step-07-health-check.mdYes

Invocation Contract

AspectDetail
Inputsproject_path [required], scope_hint [optional]
Gatesstep-02: Confirm Gate [C]
Outputsanalysis-report.md, skill-brief.yaml files (one per recommended unit)
HeadlessAll gates auto-resolve with default action when {headless_mode} is true

On Activation

  1. Load config from {project-root}/_bmad/skf/config.yaml and resolve:

    • project_name, output_folder, user_name, communication_language, document_output_language, forge_data_folder, skills_output_folder, sidecar_path
  2. Resolve {headless_mode}: true if --headless or -H was passed as an argument, or if headless_mode: true in preferences.yaml. Default: false.

  3. Load, read the full file, and then execute ./steps-c/step-01-init.md to begin the workflow.

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.