external/creative-writing-skills/cw-prose-writing/SKILL.md
Creative writing skill for drafting and editing narrative fiction prose. Use when writing new scenes, chapters, or dialogue, or when editing existing prose. Discovers and follows project-specific style guides, character voice conventions, and formatting preferences.
npx skillsauth add seikaikyo/dash-skills cw-prose-writingInstall 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.
Write narrative fiction following your project's established style and conventions.
ALWAYS check for style guidance before writing:
Look for:
CLAUDE.md - Often explains project structureWRITING.md, CONVENTIONS.md, STYLE.mdREADME.md - May contain writing instructionsCommon locations:
.cursor/rules/styles/ - Style files (.md or .skill packages).cursor/rules/ - May contain style files.ai/styles/, .ai/rules/docs/style/, style/, writing/Style guides can be:
.md).skill) created by cw-style-skill-creatorDifferent types:
Read relevant guides BEFORE writing. If writing dialogue-heavy scene, read both master and dialogue guides.
Also look for:
When NO style guides found:
Inform user:
I don't see any style guides in your project yet. I can write in
competent default prose, but you'll get better results by creating
style guides first using the cw-style-skill-creator skill.
Would you like me to:
1. Write in default style for now
2. Help you create style guides first
3. Search your project for existing style documentation
If user wants you to proceed anyway:
Search when helpful for:
While Writing:
Self-Check After:
Markdown artifact with proper formatting
The workflow:
Without style guides: Generic competent prose
With style guides: YOUR specific voice
Feel free to combine with other skills - e.g., using cw-official-docs to check character details while writing.
tools
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.