write-skill

Create, update, and verify Agent Skills for Claude Code, Codex, and Grok Build.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill write-skill-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-skill
Source: https://github.com/alvis/.agents/tree/main/plugins/governance/skills/write-skill
Command: npx skills add https://github.com/alvis/.agents --skill write-skill-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Authoring Agent Skills that work consistently across Claude Code, Codex, and Grok Build is error-prone: skills drift from repository policy, triggers collide with neighboring skills, and structural or behavioral defects go undetected until runtime. This Skill provides one governed workflow to create, update, and verify skills against a shared authoring contract. ## Core Features & Use Cases - Three routed actions: create a new reusable skill, update existing skills to align with policy, or verify structural, policy, and trigger compliance. - Portable authoring contract: enforces self-contained skill directories, strict frontmatter rules, concrete requirements.intelligence levels, and root-relative references that work across all three harnesses. - Cold-start release gate: requires fresh-agent sessions with digest-pinned evidence before any behavioral self-sufficiency claim can pass, separating paper reasoning from observed results. - Bundled validator: scripts/quick_validate.ts checks frontmatter policy, adversarial YAML forms, Markdown link integrity, and runs the official Claude plugin validator when resolvable. - Use Case: A maintainer needs to add a new skill for a recurring workflow. The Skill derives representative tasks, drafts the smallest self-contained skill, runs the portable validator, and gates release on cold-start sessions proving a fresh agent can complete the tasks from the skill alone. ## Quick Start Ask the agent to create a new Agent Skill for your workflow, or to verify an existing skill directory against the repository's authoring policy.

Frequently Asked Questions about write-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Agent Skill for Claude Code or Codex?

Use the create action: define the skill's purpose, name, and concrete trigger examples, then derive representative tasks and write the smallest self-contained SKILL.md with supporting references. The workflow finishes with structural validation and a cold-start release gate using fresh-agent sessions.

How do I validate a SKILL.md file against repository policy?

Run the bundled validator with bun run scripts/quick_validate.ts --portable targeting the skill directory. It checks frontmatter policy, Markdown link integrity, and portability, and runs the official Claude plugin validator when a containing plugin is resolvable.

Can one skill support Claude Code, Codex, and Grok Build together?

Yes. Shared skills maintain one portable SKILL.md and must avoid harness-only fields like allowed-tools or model selection. Harness-specific checks in references/harnesses.md apply only when a difference affects execution, tools, or validation.

What is the cold-start release gate for skill verification?

It is a mandatory check where a fresh agent session receives only the skill directory and raw task inputs, with results recorded against SHA-256 digests and an acceptance oracle. Paper reasoning or structural validators alone cannot produce a passing behavioral verdict.

When should I update an existing skill instead of creating a new one?

Update when an existing skill already owns the overlapping capability or trigger space. Create is only appropriate when no suitable owner exists; otherwise the workflow switches to update to avoid competing triggers.