meta

Name: meta
Author: majiayu000

Data Verified

Repo stars 330
License MIT
Author updated Live
Author repo claude-skill-registry

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Data
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 94 / 100 · audit passed
Author / version / license: @majiayu000 · MIT
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Env read
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，默认拥有全部工具权限。

Output preview meta.preview

---
name: meta
description: Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why…
category: data
runtime: no special runtime
---

# meta output preview

## PART A: Task fit
- Use case: Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why skills aren't activating, or improving skill descriptions and structure..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Required structure / SKILL.md frontmatter / Critical best practices” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why skills aren't activating, or improving skill descriptions and structure.”.
- **02** When the source has headings, the agent prioritizes “Required structure / SKILL.md frontmatter / Critical best practices” 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, read environment variables; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, read environment variables; 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.

SKILL.md SKILL.md

---
name: meta
description: Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why…
category: data
source: majiayu000/claude-skill-registry
---

# meta

## When to use
- Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why skills aren't activati…
- 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 “Required structure / SKILL.md frontmatter / Critical best practices” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; 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 "meta" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Required structure / SKILL.md frontmatter / Critical best practices
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files, read environment variables | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Guide for writing and improving Claude Code skills. Use when creating new skills, debugging why skills aren't activating, or imp…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Required structure”, “SKILL.md frontmatter”, “Critical best practices”, “Description examples”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name meta directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Required structure / SKILL.md frontmatter / Critical best practices” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Writing effective Claude Code skills

Required structure

skill-name/
├── SKILL.md (required)
├── reference.md (optional)
├── scripts/ (optional)
└── templates/ (optional)

SKILL.md frontmatter

---
name: lowercase-with-hyphens
description: Explain WHAT it does AND WHEN to use it. Include trigger terms users would say.
allowed-tools: [Read, Write, Bash]  # optional: restrict permissions
---

Critical best practices

Keep skills focused - one capability per skill
Write specific descriptions - include actual terms users would mention
Test activation - verify Claude invokes it when expected
Use allowed-tools - restrict permissions for security

Description examples

❌ Bad: "Helps with data" ✅ Good: "Analyze Excel spreadsheets, generate pivot tables, create charts. Use when working with .xlsx files."

❌ Bad: "Manages configuration" ✅ Good: "Read and update YAML/JSON config files. Use when modifying settings, environment variables, or application configuration."

Debugging checklist

If Claude doesn't use your skill:

Description lacks trigger terms users would say
YAML syntax errors (check --- markers, indentation)
Description not specific enough about WHEN to use it
Wrong file path or permissions

Finding and fixing frontmatter issues

Check if frontmatter exists:

# View first 10 lines of SKILL.md
head -10 ~/.claude/skills/*/SKILL.md

Common frontmatter problems:

Missing frontmatter block - File starts with # instead of ---
- Fix: Add YAML block at top of file
Missing closing --- - Only one --- marker
- Fix: Ensure both opening and closing markers exist
Missing required fields - No name: or description:
- Fix: Add both required fields
Wrong indentation - YAML is indentation-sensitive
- Fix: Use 2 spaces, no tabs
Missing description trigger terms - Generic description
- Fix: Add specific keywords users would say

Validation script:

# Check all skills for frontmatter
for skill in ~/.claude/skills/*/SKILL.md; do
  echo "=== $skill ==="
  if head -1 "$skill" | grep -q "^---$"; then
    echo "✓ Has frontmatter"
  else
    echo "✗ Missing frontmatter"
  fi
done

Systematic skill debugging workflow

When debugging skills that aren't working:

List all skills - Verify skill exists
```
ls -la ~/.claude/skills/
```

Check frontmatter - Validate YAML structure

head -10 ~/.claude/skills/skill-name/SKILL.md

Verify required fields - Ensure name and description exist
- name: must match directory name
- description: must include trigger terms
Test description specificity - Does it explain WHEN to use?
- Include file types, actions, or domain terms
- Avoid generic phrases like "helps with" or "manages"
Check allowed-tools - If restricted, verify needed tools included
```
allowed-tools: [Read, Write, Edit, Bash, Glob, Grep]
```
Review content - Ensure instructions are clear and actionable

Skills vs slash commands

Use skills for:

Complex workflows with multiple files
Automatic contextual invocation
Comprehensive capabilities

Use slash commands for:

Simple single prompts
Manual explicit control
Quick frequently-used operations

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add majiayu000/claude-skill-registry/skills/data/meta -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

94 / 100

Verified

未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
majiayu000/claude-skill-registry
License: MIT
中文

More by @majiayu000

Category & tags

Category Data