external/creative-writing-skills/cw-brainstorming/SKILL.md
Creative writing skill for capturing story brainstorming. Use when the user is exploring narrative ideas, discussing characters, planning episodes, or thinking through story possibilities. Creates minimal working notes that preserve creative freedom by recording only what was stated and marking sources.
npx skillsauth add seikaikyo/dash-skills cw-brainstormingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Capture story brainstorming in working note format that preserves creative freedom.
Record brainstorming WITHOUT:
AI suggestions are valuable but must be clearly marked and kept minimal.
This skill handles all brainstorming types:
All share core principles (minimal capture, source tagging, preserve vagueness). See references/ for specialized guidance:
chapter-planning.md - Capturing beat and scene explorationworldbuilding.md - Exploring fictional world elements (use web search for research)character-development.md - Exploring motivations, arcs, relationshipscontinuity-timeline.md - Timeline tracking and contradiction handlingRecord ONLY what the user explicitly states. Do NOT add elaborations, examples they didn't give, or details to fill gaps.
The problem is mixing, not suggesting:
❌ User: "Character A competes with B" → Capture: "A and B compete for leadership through a tournament with three rounds..." ✅ User: "Character A competes with B" → Capture: "A and B compete" + optional: "<AI>Tournament? Political? Trial?</AI>"
Default: Untagged = user said it. Most ideas come from the user, so treat them as the default.
ONLY use tags for special context:
<AI>...</AI> - AI suggestions/possibilities (MUST be clearly wrapped)
<AI>Competition could be: tournament-style, political maneuvering, or trial-based</AI><hidden>...</hidden> - Author-only information meant to be revealed later
<hidden>Z secretly wants them both to fail so he can reclaim leadership</hidden>When to offer AI suggestions:
When to stay minimal:
Keep it vague if user leaves it vague:
Working notes can contain contradictions and multiple possibilities. Don't resolve them - just list the options being considered.
Use whatever structure fits the discussion. Could be:
Essential elements:
<AI> tags<hidden> tags when relevantOptional sections based on discussion:
"I'm thinking character X and character Y compete for leadership. Maybe this creates tension with character Z who was the previous leader."
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Form of competition?
- How does Z respond?
- Outcome?
# Leadership Competition Arc
X and Y compete for leadership after Z steps down. Z feels threatened by the challenge to his authority.
The competition unfolds in three stages:
1. Announcement and initial positioning
2. First challenge where X demonstrates strength
3. Second challenge where Y shows wisdom
...
[20 more invented beats]
Why bad? Added massive elaboration the user never stated.
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
Open questions:
- Competition format: <AI>tournament-style? political maneuvering? trial-based?</AI>
- Z's response: <AI>oppose both? support one? stay neutral?</AI>
- Resolution?
# Leadership Competition Notes
- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
- <hidden>Z is secretly manipulating both X and Y to destroy each other, planning to reclaim power after they're both discredited</hidden>
Open questions:
- Competition format?
- Outcome?
Why use <hidden>? The manipulation twist is planned for later reveal. Readers/characters don't know yet, but the author needs to track it while brainstorming.
Stop if you're writing:
Wrap AI suggestions in <AI> tags, keep minimal (2-3 options).
Good: User says "Yes, that's what I said" Bad: User says "I never said all that"
Notes should feel skeletal and incomplete. That's the point - preserves creative freedom.
DON'T just write notes and stop. After capturing, engage with the user to help develop ideas:
Useful follow-ups:
Keep it conversational:
The goal: Help the user think through their ideas, not take over the creative process.
Feel free to combine with other skills when helpful (e.g., using cw-official-docs to document finalized worldbuilding, or cw-story-critique to analyze what you're brainstorming).
brainstorm-[topic].mdtools
Conduct comprehensive GDPR compliance assessments by evaluating data processing activities against EU Regulation 2016/679, including Article 30 records of processing, lawful basis validation, data subject rights implementation, Data Protection Impact Assessments (DPIAs) under Article 35, breach notification procedures, international transfer safeguards (SCCs, adequacy decisions), and technical/organizational measures under Article 32. Use when processing personal data of EU residents, preparing for supervisory authority audits, implementing privacy-by-design for new systems, scoping compliance gaps for M&A due diligence, assessing third-party processors, or responding to data subject access requests at scale. Incorporates 2026 guidance from ICO, EDPB, and post-Data (Use and Access) Act 2025 UK-GDPR considerations. Do not use for implementing specific Article 32 controls — use implementing-gdpr-data-protection-controls; or for DSAR automation — use implementing-gdpr-data-subject-access-request.
tools
Parse Windows forensic artifacts—$MFT/$J (MFTECmd), Prefetch (PECmd), registry hives (RECmd), shellbags, and Amcache—into normalized CSV/JSON with Eric Zimmerman's EZ Tools, then load results into Timeline Explorer for analysis. Use during DFIR/incident-response investigations, after triage collection (e.g. with KAPE), to establish program execution, file/folder access, and persistence evidence from acquired forensic images.
development
Build automated multi-turn adversarial attacks against conversational LLM targets using Microsoft PyRIT's RedTeamingOrchestrator, CrescendoOrchestrator (gradual escalation), and TreeOfAttacksWithPruningOrchestrator (adaptive branching), with scorer feedback loops and persisted conversation memory. Use when single-shot LLM scanning is insufficient and you need multi-turn, scorer-driven AI red-team campaigns against a chatbot or agent.
testing
Stand up MISP, enable and cache curated threat feeds (CIRCL, abuse.ch, Feodo Tracker), apply warninglists to suppress false positives, query indicators with PyMISP, and export attributes as auto-generated Suricata/Sigma/Wazuh detection rules. Use when maturing a MISP instance to actively drive detection, curating threat feeds with quality controls, or automating IOC-to-detection pipelines for the SIEM/IDS.