Skip to content

armelhbobdad/oh-my-skills / .claude/skills/skf-export-skill

skf-export-skill

Verified

Exports an SKF skill, validating its package, writing its context snippet and updating the managed section in CLAUDE.md, AGENTS.md or .cursorrules. Use when the user requests to "export a skill" or "package a skill."

references/package.md

View on GitHub
---
nextStepFile: 'generate-snippet.md'
---

<!-- Config: communicate in {communication_language}. Render the package status in {document_output_language}. -->

# Step 2: Package

## STEP GOAL:

To report each skill's package status from the export-gate verdict step 1 §2 retained, without checking the package again.

## Rules

- Read the verdict, never re-derive a check it covers, and never modify the package
- Auto-proceed when complete
- **Multi-skill mode:** when step 1 loaded more than one skill (`len(skill_batch) > 1`), report one row per skill, each from its own verdict. See step 1 §1c.

## MANDATORY SEQUENCE

### 1. Read the Verdict

Use the export-gate JSON step 1 §2 retained for `{resolved_skill_package}`. Only when it is not in context, run `python3 {validateOutputHelper} {resolved_skill_package} --export-gate` again: the same package gives the same verdict. Step 1 §2 halts on `NOT_READY`, so `export_status` is `READY` or `WARNINGS` here.

### 2. Report Package Status

"**Package checked.**

**Status:** {export_status}
**references/:** {the count of `.md` files under `{resolved_skill_package}/references/`, or none}

{If export_status is WARNINGS:}
**Warnings** (none of them stops the export):
- {the `field` of each `validation.metadata.recommended_missing` entry, each path in `validation.crossref_7b.orphans`, and the message of each low issue in `validation.metadata.issues`, such as an empty `exports` array or a forge tier in an older stack's `confidence_tier`}"

### 3. Proceed to Snippet Generation

Display: "**Proceeding to snippet generation...**"

Auto-proceed (no user choices): load, read entirely, and execute `{nextStepFile}`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall