writing-skills

Create, review, and validate project skill files for AI coding agents.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill writing-skills-marcel-carrillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Marcel-Carrillo/ProyectosIA/tree/main/ai-specs/skills/writing-skills
Command: npx skills add https://github.com/Marcel-Carrillo/ProyectosIA --skill writing-skills-marcel-carrillo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using Claude Code, Cursor, and OpenSpec need consistent, safe, reusable skill files, but poorly written skills cause agents to over-read context, require unavailable tools, or violate project business rules. This Skill enforces a canonical structure, frontmatter format, and guardrails for authoring skills. ## Core Features & Use Cases - Skill authoring standards: Defines naming rules, YAML frontmatter requirements, description conventions, and a recommended SKILL.md structure. - Guardrails and tool policy: Enforces selective context loading, explicit external tool rules (GitHub, Context7, Jira, Sentry, browser MCPs), and ecommerce domain safety rules. - Review and testing workflow: Provides a review checklist, proportional testing levels, and pressure-scenario templates for high-risk skills like commit or code-auditing. - Use Case: When adding a new update-docs skill to the repository, use this Skill to generate valid frontmatter, scoped context loading, and guardrails, then validate it against the review checklist before syncing agent mirrors. ## Quick Start Ask the agent to create a new project skill named update-docs following the writing-skills standards and validate it against the review checklist.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a new skill for Claude Code or Cursor?▼

Create a folder under ai-specs/skills/<skill-name>/ containing a SKILL.md file with YAML frontmatter (name, description, author, version) and a focused markdown body. The name must match the folder, and the description should start with 'Use when' to trigger discovery.

What frontmatter fields does a SKILL.md file require?▼

A SKILL.md requires name and description in its YAML frontmatter; this project also requires author and version. The name must match the folder name, and the description should state when to load the skill rather than summarizing the whole workflow.

How should skills handle external tools like Jira, Sentry, or Context7?▼

Skills must not require Jira or Sentry by default, and Context7 is allowed only when available in the current agent environment. GitHub tools are allowed only when branches, commits, or pull requests are relevant to the task.

When should I not create a skill?▼

Do not create a skill for one-off instructions, content that belongs in docs/, feature-specific changes that belong in OpenSpec, or rules better enforced by a script. Skills are for recurring workflows needing consistent agent behavior.

How do I test a high-risk skill like commit or code review?▼

Use proportional testing: basic frontmatter review for small edits, scenario checks for medium-risk changes, and pressure scenarios for high-risk skills. Pressure tests verify the skill prevents tempting mistakes like committing without verification or exposing supplier data.