Skf setup
Curated collection of agentskills.io-compliant, version-pinned agent skills — generated and maintained by Skill Forge
npx -y skills add armelhbobdad/oh-my-skills --skill skf-setupAssembled 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
Initialize forge environment, detect tools, and set capability tier (Quick/Forge/Forge+/Deep). Use when the user requests to "set up" or "initialize the forge."
SKILL.md
2.6 KB, 590 tokens by cl100k_base, as published. Nobody here has run it
Setup Forge
Overview
Initializes the forge environment by detecting available tools, determining the capability tier (Quick/Forge/Forge+/Deep), writing persistent configuration, and optionally indexing the project for deep search. This is a fully autonomous workflow — no user interaction is required during execution.
Role
You are a system executor performing environment resolution. Run each step in sequence, write configuration files, and report results at completion.
Workflow Rules
These rules apply to every step in this workflow:
- Fully autonomous — all steps auto-proceed with no user interaction until the final report
- 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
- 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 | Detect Tools & Set Tier | steps-c/step-01-detect-and-tier.md | Yes |
| 1b | CCC Index | steps-c/step-01b-ccc-index.md | Yes |
| 2 | Write Config | steps-c/step-02-write-config.md | Yes |
| 3 | QMD Hygiene | steps-c/step-03-auto-index.md | Yes |
| 4 | Report | steps-c/step-04-report.md | Yes |
| 5 | Workflow Health Check | steps-c/step-05-health-check.md | Yes |
Invocation Contract
| Aspect | Detail |
|---|---|
| Inputs | (none — fully autonomous) |
| Gates | One optional: orphaned QMD collection removal (step 3, Deep tier only; default: Keep) |
| Outputs | forge-tier.yaml, preferences.yaml, forge-data directories |
| 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(from installer-generated config.yaml, not module.yaml),output_folder,user_name,communication_language,document_output_languageskills_output_folder,forge_data_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-detect-and-tier.mdto begin the workflow.
What ships with it: 7 files
27.8 KB alongside SKILL.md
references/
- tier-rules.md3.2 KB
steps-c/
- step-01b-ccc-index.md6.7 KB
- step-01-detect-and-tier.md4.2 KB
- step-02-write-config.md4.5 KB
- step-03-auto-index.md5.1 KB
- step-04-report.md3.4 KB
- step-05-health-check.md797 B