skill-authoring-edho-ferdian

Governs creation, validation, compliance testing, and packaging of Claude Code skills.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill skill-authoring-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/skill-authoring-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill skill-authoring-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building their own AI skill collections often duplicate existing skills, write descriptions that never trigger, ship instructions nobody follows, and let packaged archives drift out of sync with source. This Skill provides the authoring discipline that prevents those failure modes. ## Core Features & Use Cases - Search-before-build workflow: Checks local skills, marketplaces, GitHub, and the web (in cost order) with a security vetting pass on any external skill before adoption. - Quality bar and compliance testing: Defines what makes a skill done (triggering description, stated boundaries, provenance) and measures whether agents actually obey a skill using supportive, neutral, and competing prompt levels. - Packaging and canonical contracts: Validates frontmatter, packages skills into deterministic dist/*.skill archives via package_skills.py, and hosts shared contracts for language routing, the seven-stage development loop, Context7 docs lookup, and surgical code changes. - Use Case: Before adding a new skill to the repo, run the search sequence to confirm nothing similar exists, write it to the quality bar, then run python scripts/package_skills.py <name> so CI's drift check passes. ## Quick Start Ask the agent to check whether a skill for your intended task already exists and, if not, draft a new SKILL.md following this ecosystem's quality bar and package it into dist.

Frequently Asked Questions about skill-authoring-edho-ferdian

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

FAQPage Schema
How do I create a new Claude Code skill without duplicating existing ones?

Search in cost order before building: first the local skills/ tree, then installed and marketplace skills, then GitHub via gh search, then at most three web queries. A near-match locally usually means folding a new references file into an existing skill rather than creating a new one.

How do I test whether an AI agent actually follows a skill?

Run the same task at three prompt strictness levels: supportive (naming the skill), neutral (using only its trigger phrases), and competing (nudging toward a forbidden shortcut). Report the compliance rate and tool-call sequence; failing neutral indicates a description problem, failing competing indicates a rules problem.

How do I package a skill into a .skill archive for Claude.ai upload?

Run python scripts/package_skills.py with an optional skill name after validating with validate_skills.py. The script writes forward-slash paths and a fixed timestamp for byte-identical output, and CI fails the build if dist/ drifts from skills/.

What makes a skill description trigger reliably?

The description must name concrete phrases users actually say, including Indonesian ones in this ecosystem, and state what the skill is not for when a neighboring skill exists. A description that is accurate but never fires is treated as a dead skill.

When should a repeated principle become a rule instead of staying in skills?

When the same principle appears in three or more skills, promote it into a shared rule file. Collect occurrences mechanically with grep across skills/**/*.md, then replace the duplicated passages with a cross-reference to the canonical contract.

What are the limitations of the automated skill validation?

validate_skills.py checks frontmatter, description length, forbidden mentions, and broken reference links, but it does not detect absolute local paths or leaked secrets. Those require human judgment and remain part of a manual audit pass, not the CI gate.