القائمة
Create or refactor high-quality skills with lean frontmatter, progressive disclosure, and optional bundled helpers. Use when authoring reusable agent workflows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skill-authoring-guide |
| description | Create or refactor high-quality skills with lean frontmatter, progressive disclosure, and optional bundled helpers. Use when authoring reusable agent workflows. |
Use this skill when creating or improving a reusable skill.
name and description — the description must be specific enough to avoid false triggers.SKILL.md and move bulk detail into references/ or scripts/.---
name: kebab-case-matching-directory-name
description: Use when [trigger condition]. Does [what it does]. [Optional: NOT for X.]
---
Default to a pure Markdown body after the YAML frontmatter. Use headings such as ## Purpose, ## When to Use, ## Workflow, and ## Verification. Do not use XML-like tags such as <Purpose>, <Workflow>, or <Use_When> as normal top-level sections. XML-like tags are acceptable only when they strictly delimit nested examples, quoted input, external documents, or machine-readable prompt payloads.
Good description (specific, trigger-clear):
Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, and method allowlists.
Weak description (too broad, won't trigger reliably):
Helps with MCP things and file access.
name must match the directory name exactly.description must say what the skill does AND when to use it in one sentence.SKILL.md should be readable in one focused pass — target 50–120 lines.references/.scripts/.SKILL.md exceeds 150 lines, split off the excess into a reference file.SKILL.md: core workflow, when to use, safety constraints.references/: detailed patterns, full checklists, long examples.scripts/: automation helpers.references/ links that point to non-existent files.| Section | Target |
|---|---|
| Frontmatter description | 1 sentence, 15–30 words |
SKILL.md body | 50–120 lines |
| Individual workflow steps | 1–3 lines each |
| References total | as needed, not in SKILL.md |
scripts/init_skill.py — scaffold a new skill directoryscripts/package_skill.py — package for distributionscripts/quick_validate.py — check frontmatter and dead referencesUse them as optional helpers if they fit your workflow.
Use hard-won-skill-extractor when the challenge is turning a hard-earned session into a reusable skill candidate.
Use when starting work in a repository with Agent Powerups installed, when a task may match a reusable local skill, command, workflow, hook recipe, AGENTS.md template, or MCP feature.
Use when validating rendered web pages, local dev servers, browser automation, screenshots, forms, auth sessions, or UI evidence with strict browser safety boundaries.
Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.
Use when implementing any feature or bugfix, before writing implementation code
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Use when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or blind implementation.