command-management
Create Consistent Custom Slash Commands
Custom slash commands can become inconsistent, over-permissioned, or hard to test. This skill guides command creation with a template, least-privilege tool choices, and SlashCommand validation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "command-management" from https://skillstore.io/skills/emz1998-command-management.md and its manifest at https://skillstore.io/api/skills/emz1998-command-management/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "command-management". Create a command for reviewing pull requests before merge.
Expected outcome:
- A project command plan with name, purpose, frontmatter fields, least-privilege tools, workflow phases, rules, and acceptance criteria.
- A validation note showing the SlashCommand test result or the reason testing was unavailable.
Using "command-management". Update our release checklist command to include security review.
Expected outcome:
A revised command structure that keeps existing sections, adds security review tasks, and records the validation result.
Using "command-management". Check whether this command grants too many tools.
Expected outcome:
A permission review that identifies broad tool access, suggests narrower entries, and keeps only tools required for the workflow.
Security Audit
SafeAll 18 static findings are false positives after context review. The shell-looking hits are Markdown examples or inline code markers, and the home-directory paths are documentation for Claude Code command locations. No evidence of prompt injection, exfiltration intent, or hidden execution was found.
Risk Factors
โ๏ธ External commands (8)
๐ Filesystem access (10)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emz1998-command-management/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emz1998-command-management?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emz1998-command-management?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emz1998-command-management/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emz1998-command-management.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
Emz1998. (2026). command-management security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/emz1998-command-management/audits/6BibTeX citation
@techreport{emz1998-emz1998-command-management-2026,
author = {Emz1998},
title = {command-management security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/emz1998-command-management/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "command-management security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "Emz1998"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/emz1998-command-management/audits/6"
identifiers:
- type: other
value: "skillstore:emz1998-command-management:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize Team Commands
Engineering leads can create shared project commands with consistent frontmatter, permissions, and acceptance criteria.
Update Existing Workflows
Developers can revise command files while preserving the expected template structure and least-privilege tool rules.
Prepare Agent Workflows
AI workflow maintainers can turn recurring prompts into reusable commands for Claude Code sessions.
Try These Prompts
Create a project slash command named [name] for [task]. Use the included template and choose the least permissions needed.
Review the current command at [path]. Update it for [new behavior] while preserving frontmatter, rules, and acceptance criteria.
Create a shared command for [workflow]. Include clear phases, argument hints, allowed tools, and test it with SlashCommand.
Inspect the command for [workflow]. Reduce tool permissions, clarify prohibited actions, update acceptance criteria, and run the available SlashCommand test.
Best Practices
- Keep commands concise and focused on one repeatable workflow.
- Grant only the tools needed for the command task.
- Test each command after creation or update, then report the result.
Avoid
- Creating commands with broad tool permissions when narrow rules would work.
- Saving commands outside the approved project command directory.
- Skipping the template sections or leaving placeholders in final commands.
Frequently Asked Questions
What does this skill create?
Does it manage built-in slash commands?
Can it create personal commands in the home directory?
How does it handle permissions?
Does it test commands?
Can teams use these commands?
Developer Details
Author
Emz1998License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
26421118b848d9f1efc0aa169d8a7a9e7e0a877e
Maintenance freshness
7/22/2026
Usage
4 downloads ยท 119 views
File structure