gigaverse-app/skillet
Overview
This skill helps you brainstorm and validate names for plugins, skills (atoms), agents, and commands following a clear, consistent convention. It produces neutral noun prefixes, generates matching -ing skills, role-noun agents, and imperative commands, then validates the set for clarity and conflicts. Use it to get memorable, pronounceable, and convention-compliant names quickly.
How this skill works
I start by identifying the domain in 3–5 words (what the plugin does). I transform that domain into neutral noun candidates (e.g., -smith, -forge, -kit, meta-). For each prefix I generate matching atom names: skills end with -ing, agents use role nouns (-er/-or), and commands use the base verb form. Finally, I validate names against a checklist: neutral prefix, correct suffixes, no type postfixes, pronounceability, memorability, and conflict risk.
When to use it
- Naming a new plugin or deciding a shared prefix for related atoms
- Brainstorming alternative neutral-prefix candidates (skillsmith, codeforge, datakit, metaskill)
- Validating that existing names follow the convention and are consistent
- Choosing atom names: -ing skills, -er/-or agents, and imperative commands
- Checking for ambiguous or conflicting meanings before publishing
Best practices
- Make the plugin name a neutral noun that serves as the common prefix (avoid verb-like prefixes)
- Use -ing for skills, -er/-or or natural role nouns for agents, and base verbs for command routes
- Avoid explicit type postfixes like -skill, -agent, or -command; the directory indicates type
- Prefer short, pronounceable, and distinctive prefixes to improve recall
- When -ing feels awkward, rephrase the activity (e.g., trigger-tuning vs. triggering)
Example use cases
- Domain: creating skills → prefix ideas: skillsmith, skillforge, skillkit; atoms: skillsmith-authoring, /skillsmith-create
- Domain: reviewing code → prefix ideas: codeforge, codeguard; atoms: codeforge-reviewing, codeforge-reviewer, /codeforge-review
- Validate existing names: detect verb-form prefixes like skill-authoring- and recommend neutral alternatives
- Generate a table of prefix → skill → agent → command to check consistency before release
- Resolve ambiguous -ing meanings by suggesting clearer -ing or alternate role names
FAQ
A neutral prefix is a noun (place, tool, or role) rather than a verb form. It matters because it stays stable as a common prefix for mixed atom types and avoids awkward double-verb constructions.
What if -ing sounds awkward for a particular activity?
Rephrase the activity into a clearer gerund or use a more specific noun role (e.g., trigger-tuning, trigger-designer) to avoid confusion.
Should I check for name conflicts globally?
Yes. After you shortlist names, search existing plugins and packages to avoid collisions and confusingly similar names.
7 skills
This skill brainstorms and validates plugin and atom names using neutral nouns and naming conventions to ensure consistent, memorable identifiers.
This skill helps you adopt type hints and fix type errors with Pyright or Basedpyright without changing runtime behavior.
This skill helps you perform code review across diffs and PRs, focusing on architecture and cross-file patterns to improve quality.
This skill guides packaging and structuring Claude Code plugins, enabling clean plugin.json placement and organized components for distribution.
This skill optimizes trigger keywords and frontmatter description to reliably activate the metaskill, ensuring specificity and keyword-variants.
This skill helps you discover code patterns before writing new code, enabling reuse, consistency, and cleaner architectures across projects.
This skill reviews code diffs at PR level, highlighting cross-file architectural issues and high-impact egregious problems for faster fixes.