fan-agent-skill-authoring

Author and validate in-repo SKILL.md files with frontmatter rules and peer-matched structure.

38|6|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/7757/Fan-Browser-Agent --skill fan-agent-skill-authoring-7757
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fan-agent-skill-authoring
Source: https://github.com/7757/Fan-Browser-Agent/tree/main/skills/software-development/fan-agent-skill-authoring
Command: npx skills add https://github.com/7757/Fan-Browser-Agent --skill fan-agent-skill-authoring-7757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a new skill inside the fan-agent repository requires matching strict validator constraints and peer conventions, and mistakes like wrong frontmatter placement or using the wrong creation tool silently produce invalid or misplaced skills. ## Core Features & Use Cases - Validator Rules Reference: Documents the exact frontmatter requirements enforced by tools/skill_manager_tool.py, including the 1024-character description limit and 100,000-character file cap. - Peer-Matched Structure: Provides the standard section layout (Overview, When to Use, Common Pitfalls, Verification Checklist) used by every skill under skills/software-development/. - Workflow Guidance: Covers surveying peer skills, drafting with write_file, local YAML validation, and committing to git, plus pitfalls like the session skill-loader cache. - Use Case: When asked to add a reusable workflow skill to the fan-agent repo on a branch, follow this skill to place the file at skills/<category>/<name>/SKILL.md, validate it locally, and commit it correctly. ## Quick Start Create a new in-repo skill for the fan-agent repository following the authoring conventions and validator rules.

Frequently Asked Questions about fan-agent-skill-authoring

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

FAQPage Schema
How do I create a new skill in the fan-agent repository?▼

Write the file to skills/<category>/<name>/SKILL.md using write_file, then git add and commit on the active branch. Do not use skill_manage(action='create'), which targets the user-local ~/.fan/skills/ tree instead of the repo.

What frontmatter fields are required in a SKILL.md file?▼

The validator requires the file to start with --- at byte zero, close with a --- line, parse as a YAML mapping, and include name and description fields. Version, author, license, and metadata are not enforced but match every peer skill.

What is the maximum description length for a SKILL.md?▼

The description field is limited to 1024 characters, enforced as MAX_DESCRIPTION_LENGTH by the validator. The full SKILL.md file is capped at 100,000 characters, with peer skills typically ranging from 8,000 to 14,000 characters.

Why doesn't my new skill appear in skills_list after creation?▼

The skill loader is initialized at session start and cached, so the current session will not see newly created skills. Verify the skill in a fresh session or via skill_view using the exact path; this is expected behavior, not a bug.

When should I edit an existing skill versus create a new one?▼

Survey peers with ls skills/<category>/ and read 2-3 existing SKILL.md files before creating. Prefer extending an existing skill over creating a narrow sibling that duplicates coverage; use skill_manage patch for small fixes and write_file for rewrites.