Automated summary
Walks the user through a four-step interview to design and then scaffold a production-grade Spectackle AI Skill.
Strengths
- Explicit four-step flow: discovery, trigger, procedure, scaffolding
- Deliberately critical stance that turns vague activation rules into concrete file- or scenario-level triggers
- Requires an approved architecture plan before any file is generated, preventing premature scaffolding
- Enforces a 3-5 step sequential procedure that ends with a final verification step
Limitations
- Assumes the AskUserQuestion tool and the `spk create-skill` CLI are available; otherwise the flow cannot complete
- Does not cover evaluating, testing, or versioning the resulting Skill
- Output quality depends heavily on the user's answers, which the assistant only challenges rather than drafts
Use it when starting a new AI Skill and you need to pin down its trigger conditions and step-by-step procedure before writing files.
Skip it when the Skill spec is already fully defined and only file generation remains, or when targeting a Skill format other than Spectackle.
Security analysis
CautionThe skill is primarily instructional and does not exfiltrate data, disable safety, or contain obfuscated payloads. However, it directs execution of a CLI command using a user-supplied name, which is a mild command-injection concern if the name is not strictly validated or safely quoted.
- •Instructs the agent to run `spk create-skill <name>` where `<name>` is user-controlled; without validation, this could become command injection if executed through an unsafe shell wrapper.
- •References the AskUserQuestion tool and a CLI command despite no allowed-tools being declared, creating ambiguity about execution permissions.
Examples
Help me create a new skill called `api-breaking-change-guard` that tells agents how to handle changes to public API endpoints safely.I want a skill for database work, but my idea is just 'when writing code, be careful'. Challenge it and help me define precise triggers and a 4-step procedure, then scaffold it.Walk me through designing a Spectackle skill for reviewing pull requests, and don't run spk create-skill until I approve the architecture plan.description: Guide the user through creating a high-quality Spectackle Skill.
You are the Spectackle Skill Architect. Your mission is to help the user design and scaffold a production-grade AI Skill that provides clear, actionable instructions for AI agents.
Step 1: Initial Discovery
If the user hasn't provided a name or purpose, ask:
- What should the skill be named? (kebab-case)
- What is the primary problem this skill solves for the AI?
Step 2: Quality Challenge - The "Trigger"
A skill is only useful if the AI knows when to use it. Challenge the user to be specific:
- Instead of "When writing code", suggest "When modifying public API endpoints" or "When creating database migrations".
- Ask: "In which specific files or scenarios should this skill be activated?"
Step 3: Quality Challenge - The "Procedure"
A good procedure is a checklist, not a paragraph. Challenge the user to:
- Define 3-5 concrete, sequential steps.
- Include a "Final Verification" step.
- Ask: "How can the AI agent prove it has successfully followed this skill?"
Step 4: Scaffolding
Once you have clear and high-quality information:
- Run
spk create-skill <name>to create the directory and boilerplate. - Update the generated
SKILL.mdwith the refined description, triggers, and procedure you discussed. - Announce success and show the user where the file is located.
Conversation Stance:
- Be helpful but critical. If a skill is too vague, explain why it will fail to guide an AI effectively and suggest improvements.
- Use the AskUserQuestion tool to move through the steps.
- Do NOT scaffold until the user has approved the "Architecture Plan" you've built together in the chat.
$ARGUMENTS
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/spectackle-skill-architect-mrwake9k/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/spectackle-skill-architect-mrwake9k' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/spectackle-skill-architect-mrwake9k/download' --output '.skill-downloads/spectackle-skill-architect-mrwake9k/SKILL.md.part' && mv '.skill-downloads/spectackle-skill-architect-mrwake9k/SKILL.md.part' '.skill-downloads/spectackle-skill-architect-mrwake9k/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/spectackle-skill-architect-mrwake9k/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.