SkillAgentSearch skills...

skill-creator

Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter.

Install / Use

npx skills add Gentleman-Programming/gentle-ai --skill skill-creator

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of skill-creator

skill-creator scores 87/100 on our quality scale, 1604th of 2,790 Automation skills we index.

Its SKILL.md is 3.9 KB long, split into 7 sections with 4 code examples: a solid amount of guidance for an agent.

With 9,190 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so skill-creator is actively maintained.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skill-creator compared with similar skills

All 4 of these similar skills score higher than skill-creator; compare them before choosing.

SkillScoreStarsUpdatedFormat
skill-creator (this skill)by Gentleman-Programming879.2k3d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install skill-creator?
Run npx skills add Gentleman-Programming/gentle-ai --skill skill-creator. The install tabs above show the steps for each supported agent.
Which AI agents does skill-creator work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skill-creator safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skill-creator still maintained?
The repository was last updated 3 days ago, so skill-creator is actively maintained.

name: skill-creator description: "Trigger: new skills, agent instructions, documenting AI usage patterns. Create LLM-first skills with valid frontmatter." license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"

Activation Contract

Create a skill when:

  • A pattern is used repeatedly and AI needs guidance
  • Project-specific conventions differ from generic best practices
  • Complex workflows need step-by-step instructions
  • Decision trees help AI choose the right approach

Do not create a skill when the pattern is trivial, one-off, or better served by normal documentation.

Hard Rules

  • When working in this repo, first follow docs/skill-style-guide.md as the normative source before creating or updating skills.
  • For installed global skills, use references/skill-style-guide.md as the bundled local copy of that guide when docs/skill-style-guide.md is unavailable.
  • If neither guide is available, use the compact inline rules below.
  • A skill is a runtime instruction contract for an LLM, not human documentation.
  • Do not add a Keywords section; preserve essential trigger words in description.
  • References must point to local files.
  • Keep the skill body concise: target 180–450 tokens, recommended max 700, hard max 1000.

Decision Gates

| Need | Action | |------|--------| | Code templates, schemas, fixtures, generated examples | Put them in assets/ | | Conceptual detail, edge cases, existing docs | Put local links in references/ | | Long explanation in SKILL.md | Move it to a supporting file | | Multiple meaningful paths | Add a compact decision table |

Execution Steps

  1. Check whether docs/skill-style-guide.md exists; if it does, apply it before the bundled local copy or inline fallback rules.
  2. If the repo guide is unavailable, read references/skill-style-guide.md and apply it before the inline fallback rules.
  3. Confirm the skill does not already exist and the pattern is reusable.
  4. Create or update skills/{skill-name}/SKILL.md using this required structure:
skills/{skill-name}/
├── SKILL.md              # Required - main skill file
├── assets/               # Optional - templates, schemas, examples
│   ├── template.py
│   └── schema.json
└── references/           # Optional - links to local docs
    └── docs.md           # Points to docs/developer-guide/*.mdx
  1. Use this frontmatter shape:
---
name: {skill-name}
description: "Trigger: {essential trigger words users or agents will say}. {What this skill does}."
license: Apache-2.0
metadata:
  author: "{your-github-username}"
  version: "1.0"
---
  1. Write sections in this order: Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References.
  2. Register the skill in AGENTS.md when it is a project skill.

Inline Fallback Rules

  • description MUST be one physical line, quoted, YAML-safe, and include essential trigger words first.
  • description SHOULD be <=160 chars and MUST be <=250 chars.
  • Frontmatter MUST include name, description, license, metadata.author, and metadata.version.
  • Use imperative instructions, not tutorials or background prose.
  • Put supporting material in assets/ or references/, not the main skill body.

Good:

description: "Trigger: Jira task, ticket, issue, task creation. Create Jira tasks in the team format."

Bad:

description: >
  Create Jira tasks in the team format.
  Trigger: Jira task, ticket, issue, or task creation.
Keywords: jira, task

Output Contract

Return:

  • Files created or modified.
  • Whether the repo style guide or inline fallback rules were used.
  • Any AGENTS.md registration change.
  • Any supporting files added under assets/ or references/.

References

  • docs/skill-style-guide.md — normative LLM-first skill style guide for this repo.
  • references/skill-style-guide.md — bundled local copy for installed global skills when the repo doc is unavailable.

Related Skills

View on GitHub
GitHub Stars9.2k
CategoryAutomation
Updated3d ago
Forks898

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions