Create Cmd Optimise
Optimise my PREVIOUS message into a better prompt, then save it as a slash command
Install
$ agentstack add skill-fayis672-slash-it-create-cmd-optimise ✓ 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-optimise) 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 — improve it into a stronger prompt, and save the improved version as a reusable custom slash command.
Raw arguments: $ARGUMENTS
Do this:
- Parse
$ARGUMENTSinto a name and an optional scope flag:
--global/-g/global-> save system-wide.--project/-p/project-> save to the current project.- Everything else is the command name.
- If no name is given, STOP and ask for one. A name is required.
- Determine where to save (scope):
- If a scope flag was given, use it.
- Otherwise, ASK the user with AskUserQuestion: "Where should
/be saved?" with
options Global (all projects) and Project (this repo only).
- Global path:
~/.claude/commands/ - Project path:
/.claude/commands/— create it if missing. If not
in a project, fall back to Global 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).
- Rewrite it into a clear, well-structured, high-quality prompt while **preserving the original
intent**. Apply prompt-engineering best practices:
- Make the goal explicit and unambiguous.
- Add useful structure (numbered steps, expected output format) where it helps.
- Fix grammar/spelling and tighten vague wording.
- Where the prompt clearly takes input, parameterize it with
$ARGUMENTS(or$1,$2). - Do NOT add scope the user never asked for.
- Briefly show the user a before/after diff of the prompt (1-3 lines is fine).
- Add YAML frontmatter with a one-line
descriptionand, if you added parameters, an
argument-hint.
- 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.