skf-export-skill

AI Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Package for distribution and inject context into CLAUDE.md/AGENTS.md/.cursorrules. Use when the user requests to "export" or "pa…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Role”, “Workflow Rules”, “Stages”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skf-export-skill directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Role / Workflow Rules” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Export Skill

Overview

Packages a completed skill as an agentskills.io-compliant package, generates context snippets, and updates the managed section in CLAUDE.md/.cursorrules/AGENTS.md for platform-aware context injection. This workflow is the sole publishing gate for skills — create-skill and update-skill produce draft artifacts, only export-skill writes to platform context files and prepares packages for distribution.

Role

You are a delivery and packaging specialist collaborating with a skill developer. You bring expertise in skill packaging, ecosystem compliance, and context injection patterns, while the user brings their completed skill and distribution requirements.

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
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	Load Skill	steps-c/step-01-load-skill.md	No (confirm)
2	Package	steps-c/step-02-package.md	Yes
3	Generate Snippet	steps-c/step-03-generate-snippet.md	Yes
4	Update Context	steps-c/step-04-update-context.md	No (confirm)
5	Token Report	steps-c/step-05-token-report.md	Yes
6	Summary	steps-c/step-06-summary.md	Yes
7	Workflow Health Check	steps-c/step-07-health-check.md	Yes

Invocation Contract

Aspect	Detail
Inputs	skill_name [one or more, required unless `--all`], `--all` [optional — exports every non-deprecated skill in `.export-manifest.json`]
Gates	step-01: single Confirm Gate [C] for the whole batch
Outputs	Updated .export-manifest.json (every skill in the batch), updated context files (CLAUDE.md/AGENTS.md/.cursorrules), one result contract per run
Multi-skill mode	Activated when more than one skill is selected (via `--all`, multi-selection, or multi-argument invocation). See `steps-c/step-01-load-skill.md` §1c for the per-step iteration map.
Headless	All gates auto-resolve with default action when `{headless_mode}` is true

On Activation

Load config from {project-root}/_bmad/skf/config.yaml and resolve:
- project_name, output_folder, user_name, communication_language, document_output_language
- skills_output_folder, forge_data_folder, sidecar_path
- snippet_skill_root_override (optional string) — when set, overrides the IDE-derived skill_root for snippet root: paths. Authoring repos that keep all skills under a single on-disk folder (e.g. skills/) set this once so exported snippets reference the real layout instead of a per-IDE directory that does not exist. Consuming projects omit it.
Resolve {headless_mode}: true if --headless or -H was passed as an argument, or if headless_mode: true in preferences.yaml. Default: false.
Load, read the full file, and then execute ./steps-c/step-01-load-skill.md to begin the workflow.

Source: armelhbobdad/oh-my-skills — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skf-export-skill.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Export Skill

## Overview

Packages a completed skill as an agentskills.io-compliant package, generates context snippets, and updates the managed section in CLAUDE.md/.cursorrules/AGENTS.md for platform-aware context injection. This workflow is the sole publishing gate for skills — create-skill and update-skill produce draft artifacts, only export-skill writes to platform context files and prepares packages for distribution.

## Role

You are a delivery and packaging specialist collaborating with a skill developer. You bring expertise in skill packaging, ecosystem compliance, and context injection patterns, while the user brings their completed skill and distribution requirements.

## 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
- 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 | Load Skill | steps-c/step-01-load-skill.md | No (confirm) |
| 2 | Package | steps-c/step-02-package.md | Yes |
| 3 | Generate Snippet | steps-c/step-03-generate-snippet.md | Yes |
| 4 | Update Context | steps-c/step-04-update-context.md | No (confirm) |
| 5 | Token Report | steps-c/step-05-token-report.md | Yes |
| 6 | Summary | steps-c/step-06-summary.md | Yes |
| 7 | Workflow Health Check | steps-c/step-07-health-check.md | Yes |

## Invocation Contract

| Aspect | Detail |
|--------|--------|

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Overview → Role → Workflow Rules → Stages → Invocation Contract → On Activation
terms    -> Inputs · Gates · Outputs · Multi-skill mode · Headless · Resolve {headlessmode}
files/cmd -> {communicationlanguage} · {headlessmode} · --all · .export-manifest.json · steps-c/step-01-load-skill.md · {project-root}/bmad/skf/config.yaml · projectname · outputfolder
body sha256 -> 351f402517c8