zeus-agent-skill-authoring

Author in-repo SKILL.md files with compliant frontmatter and structure.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill zeus-agent-skill-authoring-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zeus-agent-skill-authoring
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/zeus-agent-skill-authoring
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill zeus-agent-skill-authoring-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Contributing a reusable skill to the ZeusAgent repository requires meeting strict authoring standards for frontmatter, description length, platform gating, tests, and docs; this Skill walks contributors through those rules so pull requests pass review on the first attempt. ## Core Features & Use Cases - Frontmatter Standards: Enforces the repo hardline rules for name, description (60 characters max), author attribution, license, and platform gating. - Tier and Category Guidance: Helps decide between bundled skills/ and optional-skills/ placement and picking the correct category. - Tests and Docs Workflow: Covers required pytest files, docs regeneration with scope discipline, and sidebar registration. - Use Case: A contributor wants to ship a new workflow skill with the ZeusAgent package; this Skill provides the validation snippet, body section order, and verification checklist to produce a review-ready SKILL.md. ## Quick Start Ask the agent to create a new in-repo skill under skills/<category>/<name>/ following the zeus-agent-skill-authoring standards and commit it on the current branch.

Frequently Asked Questions about zeus-agent-skill-authoring

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

FAQPage Schema
How do I add a new skill to the ZeusAgent repository?▼

Write the SKILL.md with write_file to skills/<category>/<name>/ or optional-skills/<category>/<name>/, then git add and commit. Do not use skill_manage(action='create'), which only targets the user-local ~/.zeus/skills/ tree.

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

The validator requires name and description, but the repo standard also expects version, author, license, platforms, and metadata.zeus tags and related_skills. The file must start with --- at byte zero and close the frontmatter before a non-empty body.

Should a skill go in skills/ or optional-skills/?▼

Bundled skills/ is for daily-driver behavior useful across many user types, roughly five or more sessions per month. Niche, vertical-specific, or heavy skills belong in optional-skills/; when in doubt, choose optional since promoting later is easier than demoting.

Why does my new skill not appear in the current session?▼

The skill loader is initialized at session start and cached, so skill_view and skills_list will not see a newly committed skill until a new session begins. This is expected behavior, not a bug.

What are the description length limits for SKILL.md?▼

The repo hardline is 60 characters, one sentence ending with a period, even though the validator allows up to 1024. The system prompt index truncates at 57 characters, so the trigger must be self-contained in that window.