skill-forge

Solid

Meta-skill and design compass for creating new skills and upgrading existing ones with a deliberate push toward being maximally technological, creative, and aesthetically disciplined. Use when the user wants to create a skill from scratch, reshape an existing skill, make a skill more reliable/technological, more creative/varied, or more visually polished — or when a skill feels templated, generic, or mechanically weak. Trigger on phrases like "создай скил", "новый скил", "улучши скил", "сделай скил креативнее", "эстетичный скил", "технологичный скил", "скилл выглядит шаблонно", "перепиши SKILL.md", even if the user does not say the word "skill" explicitly. Also use when reviewing a skill before release.

AI & Automation 5 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# skill-forge A compass, not a dictator. This skill helps you **design** skills that are maximally **technological** (engineered, reliable, composable), **creative** (generative, varied, distinctive), and **aesthetically disciplined** (intentional, not templated). It separates the *obligatory base* — rules you must not break — from *accents* — amplifiers you choose per task. > Russian triggers: `создай скил`, `новый скил`, `улучши скил`, `сделай скил > креативнее`, `эстетичный скил`, `технологичный скил`, `скилл шаблонный`, > `перепиши SKILL.md`, `мета-скилл`, `проверь скилл перед релизом`. ## Level 0 — Hard rules (the base, never break these) These come from the official Agent Skills specification (agentskills.io) plus our own working gates. They are **non-negotiable**. - **Frontmatter**: `name` (≤64 chars, `a-z 0-9 -`, no double hyphens, MUST match the folder name) and `description` (≤1024 chars, MUST state *what* the skill does AND *when* to use it). Put all "when to use" info in `description`, never in the body. Make triggers a little "pushy" to fight undertriggering — list synonyms and casual phrasings. - **Progressive disclosure**: keep `SKILL.md` under 500 lines. Bundle code in `scripts/` (deterministic, repetitive tasks), docs in `references/` (loaded as needed; add a TOC if >300 lines), outputs in `assets/`. Reference files one level deep only. - **Voice**: write in the imperative. Explain the *why* instead of heaped MUST/ ALWAYS/NEVER — all-caps...

Details

Author
bestdeejay-design
Repository
bestdeejay-design/agent-skills
Created
1 weeks ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category