Recipe Template
Template for commands that implement a structured recipe: validate preconditions, then execute numbered steps. Fork this and replace the placeholder content. The 'Context Validation Checkpoints' section is the key pattern, forcing Claude to verify preconditions before starting.
Install
$ agentstack add skill-florianbruniaux-claude-code-plugins-recipe-template ✓ 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-florianbruniaux-claude-code-plugins-recipe-template) 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
Recipe Command Template
> This is a template. Replace all [placeholder] content with your specifics.
When to Use
- [Describe the exact situation where this command applies]
- [Describe when NOT to use it, with a common misuse case]
Context Validation Checkpoints
Before executing any step, verify all of these are true. If any checkpoint fails, stop and explain why to the user.
- [ ] [Precondition 1: e.g., "The target branch exists and is up to date with main"]
- [ ] [Precondition 2: e.g., "No uncommitted changes in the affected files"]
- [ ] [Precondition 3: e.g., "Required config file exists at path X"]
- [ ] [Precondition 4: e.g., "Necessary permissions or credentials are available"]
Recipe Steps
Step 1: [Action name]
[Clear instructions for this step. Be specific about what to read, what to check, what to write.]
Validation: [How Claude verifies this step completed correctly before moving to Step 2]
Step 2: [Action name]
[Instructions]
Validation: [How to verify]
Step 3: [Action name]
[Instructions]
Validation: [How to verify]
Step 4: Confirm Completion
Summarize what was done:
- [Item 1 completed]
- [Item 2 completed]
- Files modified: [list]
- Next action for the user (if any): [instruction]
Error Handling
| Situation | Response | |-----------|----------| | [Error condition 1] | [What to do: retry / stop / ask user] | | [Error condition 2] | [What to do] | | Precondition checkpoint fails | Stop. Explain which checkpoint failed and what the user needs to fix before re-running |
Arguments
If $ARGUMENTS[0] was provided: [how to use it] If no argument was provided: [default behavior]
> The "Context Validation Checkpoints" section is the key pattern from this template. > It forces Claude to verify preconditions explicitly rather than discovering failures mid-execution. > Inspired by recurring patterns in Packmind commands (Apache 2.0).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: FlorianBruniaux
- Source: FlorianBruniaux/claude-code-plugins
- 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.