skill-authoring
- Repo stars 205
- License MIT
- Author updated Live
- Author repo GitHub-Copilot-for-Azure
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @microsoft · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- 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: skill-authoring
description: Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"c…
category: writing
runtime: no special runtime
---
# skill-authoring output preview
## PART A: Task fit
- Use case: Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new skill\", \"write a skill\", \"skill template\", \"skill structure\", \"review skill\", \"skill PR\", \"skill compliance\", \"SKILL.md format\", \"skill frontmatter\", \"skill best practices\"..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Constraints / Structure” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new skill\", \"write a skill\", \"skill template\", \"skill structure\", \"review skill\", \"skill PR\", \"skill compliance\", \"SKILL.md format\", \"skill frontmatter\", \"skill best practices\".”.
- **02** When the source has headings, the agent prioritizes “When to Use / Constraints / Structure” 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. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
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.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Constraints / Structure”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-authoring
description: Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"c…
category: writing
source: microsoft/GitHub-Copilot-for-Azure
---
# skill-authoring
## When to use
- Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new…
- 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 “When to Use / Constraints / Structure” 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. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-authoring" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Constraints / Structure
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
}Skill Authoring Guide
This skill provides guidance for writing Agent Skills that comply with the agentskills.io specification.
When to Use
- Creating a new skill for this repository
- Reviewing a skill PR for compliance
- Checking if an existing skill follows best practices
- Understanding token budgets and progressive disclosure
Constraints
name: 1-64 chars, lowercase + hyphens, match directorydescription: 1-1024 chars, ≤60 words, explain WHAT and WHEN- Use
WHEN:with quoted trigger phrases (preferred overUSE FOR:) - Avoid
DO NOT USE FOR:unless the skill has trigger overlap with a broader skill (see frontmatter guidelines) - Use inline double-quoted strings (not
>-folded scalars) - SKILL.md: <500 tokens (soft), <5000 (hard)
- references/*.md: <1000 tokens each
Structure
SKILL.md(required) - Instructionsreferences/(optional) - Detailed docsscripts/(optional) - Executable code
Frontmatter: name (lowercase-hyphens), description (WHAT + WHEN)
Progressive Disclosure
Metadata (~100 tokens) loads at startup. SKILL.md (<5000 tokens) loads on activation. References load only when explicitly linked (not on activation). Keep SKILL.md lean.
Reference Loading
References are JIT (just-in-time) loaded:
- Only files explicitly linked via
[text](references/file.md)load - Link to files, not folders -
[Recipes](references/recipes/README.md)not[Recipes](references/recipes/) - Each file loads in full (not sections)
- No caching between requests - write self-contained files
- Use recipes/services patterns for multi-option skills
See REFERENCE-LOADING.md for details.
Validation
# Run from the scripts directory
cd scripts
npm run references # Validate all skill links
npm run tokens -- check # Check token limitsIntegrity Checks
When reviewing or authoring skills, verify:
- No broken links - All referenced files exist
- No orphaned references - All reference files are linked
- Token budgets - References under 1000 tokens (split if exceeded)
- No duplicates - Consolidate repeated content
- No out-of-place guidance - Service-specific content belongs in service-specific references
See Validation for detailed procedures.
Reference Documentation
- Guidelines - Detailed writing guidelines
- Token Budgets - Limits and splitting guidance
- Reference Loading - How references load
- Checklist - Pre-submission checklist
- Validation - Link and reference validation
- agentskills.io/specification - Official spec
Decide Fit First
Design Intent
How To Use It
Boundaries And Review