Create Cmd Instruct
Reshape my PREVIOUS message using extra instructions, then save it as a slash command
Install
$ agentstack add skill-fayis672-slash-it-create-cmd-instruct ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-fayis672-slash-it-create-cmd-instruct) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
The user wants to take their previous message — the most recent user turn in this conversation before this invocation — modify it according to extra instructions they provide here, and save the result as a reusable custom slash command.
Raw arguments: $ARGUMENTS
The arguments contain a command name and instructions for how to change the prompt, separated by a | pipe. An optional scope flag may appear in the name part. Example: /slash-it:create-cmd-instruct daily-report --project | output a markdown table and ask for the date
Do this:
- Split
$ARGUMENTSon the first|.
- Left side = the command name (and optional scope flag).
- Right side = the user's instructions for reshaping the prompt.
If there is no |, treat the first token as the name and the rest as instructions.
- From the left side, extract the name and any scope flag:
--global/-g/global-> system-wide.--project/-p/project-> this project.
- If the name is empty, STOP and ask for it (required). If the instructions are empty, ask what
changes the user wants.
- Determine where to save (scope):
- If a scope flag was given, use it.
- Otherwise ASK with AskUserQuestion: "Where should
/be saved?" -> Global or
Project.
- Global path:
~/.claude/commands/ - Project path:
/.claude/commands/— create if missing; fall back
to Global if not in a project and say so.
- Normalize the name: lowercase, kebab-case, strip any leading
/and.md. - Find the user's previous prompt (the message right before this call).
- Produce a new prompt = the previous prompt transformed according to the instructions, plus
light optimisation (clarity, structure, grammar) while honoring the original intent. Parameterize with $ARGUMENTS/$1/$2 where it makes the command reusable.
- Briefly show the user the resulting prompt so they can see what was saved.
- Add YAML frontmatter with a one-line
descriptionand anargument-hintif parameters exist. - Write the file to
/.md. - If that file already exists, show its current contents and ask before overwriting.
- Confirm: print the saved file path, the scope, and that
/is now available.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: fayis672
- Source: fayis672/slash-IT
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.