Skills Command Development
📦
Command Development
v0.2.0 Content revision r1 Medium Risk ⚙️ External commands📁 Filesystem access🌐 Network access
Build Claude Code Slash Commands
Teams need reusable commands that behave consistently across projects. This skill guides command structure, frontmatter, arguments, Bash context, plugin resources, testing, and documentation.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "Command Development" from https://skillstore.io/skills/davila7-command-development.md and its manifest at https://skillstore.io/api/skills/davila7-command-development/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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 Development". User asks for a simple code review slash command.
Expected outcome:
A concise command design with description, read-only tool access, review checklist, and expected feedback format.
Using "Command Development". User asks for a plugin command that runs a quality checker.
Expected outcome:
A plugin command plan that references plugin resources, narrows Bash access, validates inputs, and summarizes checker output.
Using "Command Development". User asks how to prepare a command for marketplace distribution.
Expected outcome:
A checklist covering naming, portability, dependencies, examples, testing steps, and security review points.
Security Audit
Medium Riskv9 • 7/19/2026 Open versioned report
The 400 presented static findings are mostly documentation and test examples, with no prompt injection or malicious intent found. Copy-ready inline Bash examples that interpolate positional input remain confirmed because generated commands may permit shell injection. Broad Bash permissions and unrestricted dynamic file references also require correction, and 29 capped static matches still need manual review. Static review was capped at 400/429 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
11
Files scanned
7,237
Lines analyzed
36
Review items
0
False positives ignored
Confirmed security concerns (2)
Medium
Overly Broad Bash Permissions in Templates
Copy-ready plugin examples grant Bash(*) despite earlier advice to scope commands. Generated commands receive unrestricted shell permission beyond their stated tasks.
Both cited frontmatter examples explicitly use Bash(*), while their tasks only need narrow file or script access.
Medium
Unconstrained Dynamic File References
Copy-ready templates insert positional input into @ file references without path restrictions. Generated commands could read unintended files from absolute or traversal paths.
The examples directly concatenate $1 into file-reference paths and show no project-root containment or rejection of absolute and traversal paths.
Capability review items (36)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
Ruby/shell backtick execution
!`node ${CLAUDE_PLUGIN_ROOT}/scripts/quality-check.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/security-scan.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/perf-analyze.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/best-practices.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/pre-release-check.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/build-release.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/package.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Run plugin analyzer: !`node ${CLAUDE_PLUGIN_ROOT}/scripts/analyze.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Validate environment argument: !`echo "$1" | grep -E "^(dev|staging|prod)$" && echo "VALID" || echo
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Verify configuration available: !`test -f ${CLAUDE_PLUGIN_ROOT}/config/$1.json && echo "FOUND" || ec
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
**Execute build:** !`bash ${CLAUDE_PLUGIN_ROOT}/scripts/build.sh $1 2>&1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
**Validation results:** !`bash ${CLAUDE_PLUGIN_ROOT}/scripts/validate-build.sh $1 2>&1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Determine check level: !`echo "$1" | grep -E "^prod$" && echo "FULL" || echo "BASIC"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`node ${CLAUDE_PLUGIN_ROOT}/scripts/script-name.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Validate input: !`echo "$1" | grep -E "^pattern$" && echo "OK" || echo "ERROR"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Validate: !`echo "$1" | grep -E "^(dev|staging|prod)$" || echo "INVALID"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Test execution: !`npm test $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`gh pr view $1 --json title,body,author,files`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Files changed: !`gh pr diff $1 --name-only`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Test status: !`gh pr checks $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Deployment details: !`gh api /deployments/$1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Lint results: !`node ${CLAUDE_PLUGIN_ROOT}/bin/lint.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Step 1 - Prepare: !`bash ${CLAUDE_PLUGIN_ROOT}/scripts/prepare.sh $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Step 3 - Execute: !`${CLAUDE_PLUGIN_ROOT}/bin/execute $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Run: !`${CLAUDE_PLUGIN_ROOT}/bin/process.sh $1 $2`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Environment check: !`echo "Deploying to: $1"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Stage changes: !\`git add $1\`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Commit changes: !\`git commit -m "$2"\`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
!`node ${CLAUDE_PLUGIN_ROOT}/scripts/lint.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Validate environment: !`echo "$1" | grep -E "^(dev|staging|prod)$" || echo "INVALID"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Check file: !`test -f $1 && echo "EXISTS" || echo "MISSING"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Validate inputs: !`test -n "$1" -a -n "$2" && echo "OK" || echo "MISSING"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Try processing: !`node ${CLAUDE_PLUGIN_ROOT}/scripts/process.js $1 2>&1 || echo "ERROR: $?"`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Run tests: !`npm test $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
1. Fetch PR: !`gh pr view $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Medium
Ruby/shell backtick execution
Run analysis: !`node ${CLAUDE_PLUGIN_ROOT}/scripts/analyze.js $1`
This copy-ready inline Bash example substitutes positional command input directly into shell syntax. Without a robust argument boundary or strict allowlist, crafted input may alter the invoked command.
Risk Factors
⚙️ External commands (50)
examples/plugin-commands.md:35-42 examples/plugin-commands.md:68-71 examples/plugin-commands.md:71-74 examples/plugin-commands.md:74-81 examples/plugin-commands.md:144-147 examples/plugin-commands.md:147-150 examples/plugin-commands.md:150-153 examples/plugin-commands.md:153-161 examples/plugin-commands.md:186-188 examples/plugin-commands.md:188-202 examples/plugin-commands.md:307-336 examples/plugin-commands.md:359-361 examples/plugin-commands.md:361-363 examples/plugin-commands.md:363-369 examples/plugin-commands.md:369-371 examples/plugin-commands.md:371-380 examples/plugin-commands.md:408-411 examples/plugin-commands.md:411-412 examples/plugin-commands.md:412-413 examples/plugin-commands.md:413-414 examples/plugin-commands.md:414-417 examples/plugin-commands.md:417-418 examples/plugin-commands.md:418-427 examples/plugin-commands.md:441-442 examples/plugin-commands.md:471-472 examples/plugin-commands.md:477-478 examples/plugin-commands.md:496-497 examples/plugin-commands.md:508-509 examples/plugin-commands.md:509-510 examples/plugin-commands.md:517-520 examples/plugin-commands.md:520-521 examples/plugin-commands.md:526-532 examples/plugin-commands.md:532-533 examples/plugin-commands.md:541-543 examples/simple-commands.md:100-109 examples/simple-commands.md:175-177 examples/simple-commands.md:177-179 examples/simple-commands.md:179-181 examples/simple-commands.md:181-187 examples/simple-commands.md:212-225 examples/simple-commands.md:431-433 examples/simple-commands.md:488-492 README.md:127-128 README.md:200-201 README.md:201-202 references/advanced-workflows.md:25-28 references/advanced-workflows.md:28-36 references/advanced-workflows.md:36-56 references/advanced-workflows.md:78-79 references/advanced-workflows.md:79-81
📁 Filesystem access (29)
examples/plugin-commands.md:548 README.md:133 README.md:133 references/advanced-workflows.md:483 references/documentation-patterns.md:129 references/documentation-patterns.md:379 references/marketplace-considerations.md:42 references/marketplace-considerations.md:55 references/marketplace-considerations.md:57 references/marketplace-considerations.md:59 references/marketplace-considerations.md:88 references/marketplace-considerations.md:143 references/marketplace-considerations.md:147 references/marketplace-considerations.md:704 references/testing-strategies.md:481 references/testing-strategies.md:152 references/testing-strategies.md:152 references/testing-strategies.md:238 references/testing-strategies.md:495 references/testing-strategies.md:222 references/testing-strategies.md:223 references/testing-strategies.md:226 references/testing-strategies.md:230 references/testing-strategies.md:234 references/testing-strategies.md:238 references/testing-strategies.md:239 references/testing-strategies.md:243 SKILL.md:63 SKILL.md:63
🌐 Network access (8)
references/documentation-patterns.md:684 references/documentation-patterns.md:685 references/marketplace-considerations.md:97 references/marketplace-considerations.md:98 references/marketplace-considerations.md:99 references/marketplace-considerations.md:636 references/marketplace-considerations.md:638 references/marketplace-considerations.md:872
Audited by: codex View Audit History →
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/davila7-command-development/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/davila7-command-development?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/davila7-command-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/davila7-command-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/davila7-command-development.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
davila7. (2026). Command Development security audit report (audit version 9) [Author version 0.2.0]. Skillstore. https://skillstore.io/skills/davila7-command-development/audits/9BibTeX citation
@techreport{davila7-davila7-command-development-2026,
author = {davila7},
title = {Command Development security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/davila7-command-development/audits/9},
note = {Author version 0.2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Command Development security audit report (audit version 9)"
version: "0.2.0"
type: report
authors:
- name: "davila7"
date-released: "2026-07-19"
url: "https://skillstore.io/skills/davila7-command-development/audits/9"
identifiers:
- type: other
value: "skillstore:davila7-command-development:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
3 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Highest Skillstore Score
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
anthropics Recommended
anthropics-command-development
Skillstore Score 76
Evidence Confidence Medium
Skillstore usage 7
Updated
2026-08-21
command-development
Skillstore Score 50
Evidence Confidence High
Skillstore usage 15
Updated
2026-08-21
davila7 Current
davila7-command-development
Skillstore Score 50
Evidence Confidence Medium
Skillstore usage 6
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: Medium 59
Architecture
100
Maintainability
87
Content
70
Community
65
Spec Compliance
What You Can Build
Standardize Team Workflows
Create shared project commands for reviews, testing, documentation, and release checks.
Create Plugin Commands
Design plugin commands that use plugin resources, scripts, agents, skills, and templates.
Improve Personal Automation
Build personal slash commands for repeated development tasks across many repositories.
Try These Prompts
Create a Basic Command
Create a Claude Code slash command for reviewing changed files. Include a short description and clear instructions.
Add Arguments and Files
Design a slash command that accepts one file path argument, reads that file, and produces documentation for it.
Use Safe Bash Context
Write a command that gathers Git status before analysis. Use the narrowest allowed-tools value and explain any Bash usage.
Build a Plugin Workflow
Create a plugin slash command that validates arguments, reads a plugin template, runs a plugin script, and reports failures safely.
Best Practices
- Use the narrowest allowed-tools setting that supports the command.
- Validate and document every user-supplied argument before using it.
- Test commands with missing, invalid, long, and unusual inputs.
Avoid
- Do not grant Bash(*) when a specific command filter is enough.
- Do not pass slash command arguments directly into shell commands without validation.
- Do not hardcode personal plugin paths or local machine paths.
Frequently Asked Questions
What does this skill help me build?
It helps build Claude Code slash commands for project, personal, and plugin workflows.
Does the skill execute shell commands itself?
No. It documents command patterns that may include shell execution when users create commands.
Can I use it with plugin commands?
Yes. It covers plugin command locations, plugin resources, scripts, agents, skills, and templates.
How should I handle command arguments?
Document expected arguments, validate them early, and avoid direct shell interpolation.
Why is allowed-tools important?
It limits what a command can access or execute during a Claude Code session.
What should I review before publishing commands?
Review Bash usage, file access, argument validation, dependency assumptions, examples, and marketplace documentation.
Developer Details
Author
davila7License
MIT
Author version
v0.2.0
Skillstore revision
r1
Ref
dbe0e719813583400773166a0621f8a9b8185c72
Maintenance freshness
7/18/2026
Usage
4 downloads · 212 views