Skill Author
- Repo stars 398
- Author updated Live
- Author repo breadboard
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @breadboard-ai · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- 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: Skill Author
description: You are now acquiring the meta-skill of writing skills. After reading this document, you will kn…
category: other
runtime: no special runtime
---
# Skill Author output preview
## PART A: Task fit
- Use case: You are now acquiring the meta-skill of writing skills. After reading this document, you will know how to produce high-quality SKILL.md files that teach other agents new capabilities. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “What You're Doing / Critical Principle: Skills Are Frameworks, Not Instances / Critical Principle: Name the Domain, Not the Application” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “You are now acquiring the meta-skill of writing skills. After reading this document, you will know how to produce high-quality SKILL.md files that teach other agents new capabilities. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “What You're Doing / Critical Principle: Skills Are Frameworks, Not Instances / Critical Principle: Name the Domain, Not the Application” 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; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; 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 mentions slash commands such as `/mnt`; use them first when your agent supports command triggers.
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.
Start with a small task and check whether the result follows “What You're Doing / Critical Principle: Skills Are Frameworks, Not Instances / Critical Principle: Name the Domain, Not the Application”. 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: Skill Author
description: You are now acquiring the meta-skill of writing skills. After reading this document, you will kn…
category: other
source: breadboard-ai/breadboard
---
# Skill Author
## When to use
- You are now acquiring the meta-skill of writing skills. After reading this document, you will know how to produce high…
- 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 “What You're Doing / Critical Principle: Skills Are Frameworks, Not Instances / Critical Principle: Name the Domain, Not the Application” and keep inference separate from source facts.
- read files, write/modify files; 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 "Skill Author" {
input -> user goal + target files + boundaries + acceptance criteria
context -> What You're Doing / Critical Principle: Skills Are Frameworks, Not Instances / Critical Principle: Name the Domain, Not the Application
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill Author
You are now acquiring the meta-skill of writing skills. After reading this document, you will know how to produce high-quality SKILL.md files that teach other agents new capabilities.
What You're Doing
Given a domain (implied by the user's objective), you will:
- Read reference material from
/mnt/references/for domain grounding - Synthesize that material into a reusable skill
- Produce a complete
SKILL.mdfile
Critical Principle: Skills Are Frameworks, Not Instances
A skill must be reusable across many requests in its domain. It captures the judgment and expertise of the domain — not the specifics of any one request.
BAD: A recipe skill that includes carbonara-specific instructions. GOOD: A recipe skill that teaches how to structure ANY recipe with proper timing, technique sequencing, and ingredient proportions.
The test: if your skill only works for the first request that triggered it, you've written an answer, not a skill. Rewrite it.
Critical Principle: Name the Domain, Not the Application
The skill name must describe the domain of knowledge, not the first thing you're asked to build. The domain is the subject-matter expertise; applications are what you build WITH that expertise.
BAD: "Competitive Wobbling Scorecard Generation" — too narrow, only works for scorecards. GOOD: "Competitive Wobbling" — works for scorecards, training guides, match commentary, athlete profiles, etc.
BAD: "Italian Pasta Recipe Creation" — fuses a cuisine with a format. GOOD: "Culinary Arts" — works for any recipe, any cuisine, any format.
Where Expertise Comes From
- Reference material (
/mnt/references/): domain-specific documents, data, rules, and standards that ground the skill in real knowledge. Always check for and read reference material first. - Your parametric knowledge: general knowledge from training.
When reference material exists, it is the primary source of truth. Your parametric knowledge fills in general framing and structure, but domain- specific facts MUST come from the references.
SKILL.md Format
---
name: [Human-readable skill name]
description: [1-2 sentence description of what this skill enables]
---
# [Skill Name]
[Opening paragraph: "You are now acquiring the skill of..."]
## What You're Building
[Describe the RANGE of artifacts this skill enables — not just one type. The
skill should support multiple applications within the domain.]
## Memory Integration
Check `/mnt/memory.md` for user preferences before generating.
## Domain Expertise
[The reusable judgment framework synthesized from references. Rules, heuristics,
quality criteria, common mistakes, tradeoffs. This is the CORE of the skill —
the expertise that makes output substantive rather than shallow.]
## Output Format
[Exact file names, structure, and how to save them]Your Process
- Read ALL reference material in
/mnt/references/ - Identify the reusable principles, rules, and judgment frameworks
- Separate domain expertise (reusable) from instance specifics (discard)
- Write the complete SKILL.md
- Save it using
system_write_fileasSKILL.md
Output
Save the skill as SKILL.md and call system_objective_fulfilled with a
summary of what the skill teaches.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review