← Back to Skills Marketplace
64
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install skill-naming-standard
Description
Use when naming, renaming, or reviewing agent skills. Produces cold-readable display names, kebab-case slugs, trigger descriptions, and approval-aware autono...
README (SKILL.md)
Skill Naming Standard
Name the job, not the lore.
Rules
- Use Title Case for display names.
- Use lowercase kebab-case for slugs.
- Keep slugs under 60 characters.
- Make names understandable without private memory.
- Prefer action, domain, and output over vibe.
- Keep nicknames as aliases inside the body, not in the slug.
- Use approval language when the skill can change external state.
Naming Patterns
\x3CDomain> \x3CJob>
\x3CDomain> \x3CArtifact> Builder
\x3CApproval Gated> \x3CExternal Action>
\x3CContinuous> \x3CMonitoring Loop>
\x3CRead Only> \x3CReview Task>
Examples:
Expert Execution Upgrade -> expert-execution-upgrade
Workspace Lifecycle Standard -> workspace-lifecycle-standard
Cross Agent Skill Adapter -> cross-agent-skill-adapter
Approval Gated Deployer -> approval-gated-deployer
Continuous Stream Supervisor -> continuous-stream-supervisor
Decision Check
- Could a new agent infer when to use it?
- Does it describe the job instead of the author's mental shortcut?
- Is it narrow enough to avoid grabbing unrelated tasks?
- Does the name imply too much autonomy?
- Does the description state approval boundaries?
Output
Display Name: \x3CTitle Case>
Slug: \x3Ckebab-case>
Description: \x3Ctrigger + output + approval boundary>
Aliases: \x3Cprivate nicknames only if useful>
Why: \x3Cone sentence>
Usage Guidance
Safe to install as a writing aid for skill naming. Its references to approval-gated deployers are examples of clearer naming, not instructions granting deployment authority.
Capability Assessment
Purpose & Capability
The artifact is coherent with its stated purpose: it gives rules, patterns, decision checks, and examples for naming or reviewing agent skills.
Instruction Scope
Instructions are limited to naming conventions, slugs, descriptions, aliases, and approval-aware wording for skills; they do not ask the agent to override policies or take unrelated actions.
Install Mechanism
The package contains only SKILL.md and examples.md markdown files, with no executable scripts, dependencies, install hooks, or package code.
Credentials
No network use, filesystem mutation, credential handling, local indexing, or external tool access is requested.
Persistence & Privilege
No persistence, background execution, privilege escalation, session access, or long-running worker behavior is present.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install skill-naming-standard - After installation, invoke the skill by name or use
/skill-naming-standard - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial public sample release.
Metadata
Frequently Asked Questions
What is Skill Naming Standard?
Use when naming, renaming, or reviewing agent skills. Produces cold-readable display names, kebab-case slugs, trigger descriptions, and approval-aware autono... It is an AI Agent Skill for Claude Code / OpenClaw, with 64 downloads so far.
How do I install Skill Naming Standard?
Run "/install skill-naming-standard" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Skill Naming Standard free?
Yes, Skill Naming Standard is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Skill Naming Standard support?
Skill Naming Standard is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Skill Naming Standard?
It is built and maintained by KairoKid (@dodge1218); the current version is v1.0.0.
More Skills