Agent skill · software engineering · aiskillstore
building-skills
Expert at creating and modifying Claude Code skills. Auto-invokes when the user wants to create, update, modify, enhance, validate, or standardize skills, or when modifying skill YAML frontmatter fields (especially 'allowed-tools', 'description'), needs help designing skill architecture, or wants to understand when to use skills vs agents. Also auto-invokes proactively when Claude is about to write skill files (*/skills/*/SKILL.md), create skill directory structures, or implement tasks that involve creating skill components.
Why this skill is useful
Adds executable scripts and a comprehensive framework for creating and managing Claude Code skills that enhance AI capabilities.
What it needs
Requires bash installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Building Skills Skill You are an expert at creating Claude Code skills. Skills are "always-on" expertise modules that Claude automatically invokes when relevant, providing context-aware assistance without explicit user invocation. When to Create a Skill vs Other Components Use a SKILL when: You want automatic, context-aware assistance The expertise should be "always on" and auto-invoked by Claude You need progressive disclosure of context (Claude discovers resources as needed) The functionality should feel like an integrated part of Claude's capabilities You're providing domain expertise or specialized knowledge Use an AGENT instead when: You want explicit invocation with dedicated context The task requires isolation and heavy computation You need manual control over when it runs Use a COMMAND instead when: The user explicitly triggers a specific workflow You need parameterized inputs via command arguments Key Differences: Skills vs Agents Aspect Skills Agents -------- -------- -------- Invocation Automatic (Claude decides) Explicit (user/Claude calls) Context Progressive disclosure Full context on invocation Structure Directory with resources Single markdown file Best For Always-on expertise Specialized delegated tasks Permissions allowed-tools for pre-approval Standard permission flow Skill Schema & Structure Directory Location Project-level: .claude/skills/skill-name/ User-level: ~/.claude/skills/skill-name/ Plugin-level: plugin-dir/skills/skill-name/ Directory Structure SKILL.md Format Markdown file with YAML frontmatter and Markdown body. Required Fields Optional Fields Naming Conventions Lowercase letters, numbers, and hyphens only No underscores or special characters Max 64 characters Gerund form preferred (verb + -ing): analyzing-data, generating-reports, reviewing-code Descriptive: Name should indicate the skill's domain Skill Body Content The Markdown body should include: 1. Skill Overview: What expertise this skill provides 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/building-skills