Learn
- Repo stars 6,677
- Author updated Live
- Author repo stagewise
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @stagewise-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: Learn
description: Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting know…
category: data
runtime: no special runtime
---
# Learn output preview
## PART A: Task fit
- Use case: Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting knowledge from the current session, or updating an existing skill when the user's intentions contradicted skill guidance or content is confusing/outdated..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflows / 1. New skill from scratch / 2. Extract from conversation” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting knowledge from the current session, or updating an existing skill when the user's intentions contradicted skill guidance or content is confusing/outdated.”.
- **02** When the source has headings, the agent prioritizes “Workflows / 1. New skill from scratch / 2. Extract from conversation” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Workflows / 1. New skill from scratch / 2. Extract from conversation”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: Learn
description: Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting know…
category: data
source: stagewise-io/stagewise
---
# Learn
## When to use
- Create, extract, or update a skill. Use when authoring a new skill from scratch, extracting knowledge from the current…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Workflows / 1. New skill from scratch / 2. Extract from conversation” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "Learn" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflows / 1. New skill from scratch / 2. Extract from conversation
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Learn: write skills
Workflows
1. New skill from scratch
Trigger: "create a skill for X". Ask user intensively, follow their guidance. Build using structure + rules below.
2. Extract from conversation
Trigger: "learn-skill for what we did", "capture this", "extract a skill from above".
- Scan — collect: decisions + rationale, constraints, working patterns, workflows, gotchas, non-obvious domain facts
- Filter — keep only non-obvious, project-specific knowledge. Cut what agent already knows.
- Scope — workspace skill (
.stagewise/skills/) if content uses specific paths/tooling; user skill (.agents/skills/) if broadly reusable - Write — structure into files using rules below, write to path
→ Load references/session-extraction.md for full checklist + signal/noise examples.
3. Update existing skill
Trigger: user corrected agent behavior, overrode guidance, skill is wrong/outdated.
- Read full skill before touching anything
- Replace — overwrite wrong content. Never append "Note: above is outdated"
- Remove redundancies. Every sentence earns its place.
- Preserve what's still accurate
→ Load references/skill-updating.md for full checklist.
After every operation
Output compact summary:
- Created — path + one-line description
- Updated — path + bullets: added / replaced / removed
- Excluded — what was cut + why (extractions only)
Skill structure
skill-name/
├── SKILL.md required, target <200 lines
├── references/ optional, on-demand
│ └── *.md
├── scripts/ optional, executable scripts
└── assets/ optional, output files (templates, icons, etc.)Frontmatter (required):
---
name: skill-name
description: What it does + when to use it. Specific — drives discovery.
---No frontmatter duplication. Body must not restate description. Frontmatter = discovery blurb. Body = triggers, steps, constraints.
References section — required if any reference files exist: List every file: what it contains + when to load it. Unlisted = invisible to agent.
## References
- `references/render-loops-debugging.md` — workflow for diagnosing excess re-renders. Load when investigating render performance.Authoring rules
SKILL.md vs. references
SKILL.md → everything needed for the typical case: triggers, core steps, universal constraints.
References → content needed only sometimes:
- Workflow-specific detail (e.g. extraction checklist, update checklist)
- Examples — illustrative, not required to act
- Rules that apply only in certain cases
- Deep guidance for uncommon situations
Never put universal rules in references. Always-applies rule → SKILL.md. Agent might skip references.
The test: agent handle common case from SKILL.md alone (or + 1 reference max)? No → split is wrong. Fold needed content back into SKILL.md.
Writing style — caveman speak
Write dense. Drop articles, filler, throat-clearing. Fragments OK. Use →, =, + as connectors. Bold key terms. Keep all technical content.
| ❌ Fluffy | ✅ Caveman |
|---|---|
| "You should make sure to always read the file before editing" | "Read before edit. Always." |
| "This step is important because it ensures that..." | "→ prevents X" |
| "I'd recommend using useMemo to memoize the object" | "Wrap in useMemo." |
Rules:
- Imperative/verb-first: "Do X" not "You should do X"
- No meta phrasing: never "this skill tells you to…"
- One term per concept — never synonyms
- Every sentence must add info agent doesn't already have. Cut the rest.
Progressive disclosure
- SKILL.md → target <200 lines. Up to ~500 acceptable; split when approaching limit.
- Reference files → also target <200 lines each.
- One level deep — references link from SKILL.md only. No ref → ref chains.
Degrees of freedom
Match specificity to task fragility:
- High (prose): multiple valid approaches, context-dependent
- Medium (pseudocode/parameterized): preferred pattern exists, variation OK
- Low (exact script): fragile or order-sensitive
References
references/session-extraction.md— extraction checklist, signal/noise examples, scope decisions. Load for workflow 2.references/skill-updating.md— update checklist: conflicts, redundancy, deprecated content. Load for workflow 3.references/workflow-patterns.md— how to document per-process workflows (steps, primitives, examples). Load when skill needs to document multiple distinct processes.references/authoring-guide.md— naming, descriptions, content guidelines, anti-patterns, quality checklist. Load for comprehensive authoring guidance.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review