nodefony-skill

Create, audit, merge, and retire Agent Skills with compliance gates and trigger benchmarks.

Updated Dec 19, 2023
One-click install
npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-skill-nodefony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nodefony-skill
Source: https://github.com/nodefony/nodefony-core/tree/main/.claude/skills/nodefony-skill
Command: npx skills add https://github.com/nodefony/nodefony-core --skill nodefony-skill-nodefony

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve? Writing an Agent Skill that actually gets invoked is hard: descriptions that name tools instead of user needs never trigger, rules duplicated into CLAUDE.md make skills unreachable, and merges or removals silently orphan references. This Skill encodes the conventions, pitfalls, and verification gates needed to keep a repository of skills discoverable and conformant to the Agent Skills standard. ## Core Features & Use Cases - Skill lifecycle management: Create, edit, merge, absorb, or retire skills following naming conventions (nodefony-*), metadata.version placement, and progressive disclosure with references/ resources. - Compliance gate: The skills-doc.mjs script validates every skill against the Agent Skills standard (name format, description length, allowed frontmatter fields, dead references) and regenerates public documentation pages plus a machine-readable registry. - Trigger benchmark: The trigger-bench.mjs script measures whether real user phrases elect the right skill, catches over-broad descriptions with negative cases, and tracks trigger overlaps. - Script placement audit: The scripts-audit.mjs script classifies every repository script by whether it belongs in a skill, detects orphans and dead references, and distinguishes documented scripts from actually executed ones. - Use Case: A skill in your repository never gets invoked. Run the diagnostic procedure to check whether its rule is duplicated in CLAUDE.md, whether its triggers name the tool instead of the user need, and whether its references still resolve. ## Quick Start Ask the agent to audit why a specific skill never triggers, or to validate all skills in the repository against the Agent Skills standard before publishing.

Frequently Asked Questions about nodefony-skill

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

FAQPage Schema
How do I write an Agent Skill description that actually triggers?

Name the user need or moment, not the tool name, and write triggers as natural request formulations. Keep the description under 1024 characters in third person, stating both the capability and when to load the skill relative to the action.

Why does my skill never get invoked by the agent?

The most common cause is its rule being duplicated in CLAUDE.md, so the agent executes the rule at startup without opening the skill. Other causes are triggers naming tools instead of needs, dead references, or the underlying need no longer existing.

What fields are allowed in SKILL.md frontmatter?

The Agent Skills standard allows only name, description, license, compatibility, metadata, and allowed-tools. Version numbers belong in metadata.version, and compatibility is limited to 500 characters when present.

How do I validate skills against the Agent Skills standard?

Run the skills-doc.mjs script with the --check flag to validate name format, description length, allowed fields, and dead references across all skills. It exits with failure on hard violations and regenerates public documentation pages otherwise.

When should I merge or retire a skill instead of editing it?

Merge when several skills answer the same intent under different names, and retire only when the underlying need is proven gone. Always migrate the triggers along with the content, since an absorbed capability without its trigger phrases becomes unreachable.

What is the difference between a skill, a command, and a CLAUDE.md rule?

A skill carries a procedure the agent must follow with context and pitfalls, a command is a short human shortcut that delegates to a skill, and a CLAUDE.md rule applies permanently without being asked. Never duplicate the same rule in both CLAUDE.md and a skill.