reflect-skills-from-me…
This skill should be used when the user asks to "reflect on skills from memory", "audit marketplace skills against memory",…
Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.
$ npx -y skills add FradSer/dotclaude --skill write --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/writeContext preview
The summary Claude sees to decide when to auto-load this skill.
Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.
name: storm-write description: Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources. user-invocable: true argument-hint: "<topic> [--retrieve-top-k N] [--output-dir PATH | --save] [--force]" allowed-tools: ["Read", "Write", "Edit", "Glob", "Grep", "Bash(mktemp:*)", "Bash(mkdir:*)", "Bash(date:*)", "Task", "Skill"]
Phase 3 of the STORM pipeline. Writes each outline section in parallel (one Task subagent per section), each grounded in top-k relevant sources from the research information table, with inline `[n]` citations.
This phase is complete iff `article.md` exists and every outline section (except Introduction/Conclusion/Summary placeholders) has body text. If `--force` is not set and it exists, skip and exit early.
1. Resolve output dir. 2. Read `outline.md` and `research/sources.json`. Index sources for retrieval (simple: rank by keyword/heading overlap with the section title). 3. **Identify sections** to write — skip any whose heading is exactly "Introduction", "Conclusion", or "Summary" (these are filled in `polish`). 4. **Parallel writing** — for each section, launch ONE Task subagent (single message, parallel). Each subagent:
5. **Assemble** — concatenate sections in outline order under their headings into `article.md`. Preserve the heading hierarchy from `outline.md`. 6. Verify every non-placeholder section has body. Update `run-config.json`: `phases.write = "completed"`, section count, any TODO-flagged sections.
Report: number of sections written, number of citations used, list of sections flagged as TODO (no source), and the path to `article.md`.
A curated collection of 22 plugins for Claude Code, providing specialized agents, skills, and automation tools for development and productivity workflows.
This skill should be used when the user asks to "reflect on skills from memory", "audit marketplace skills against memory",…
Use acpx as a headless ACP CLI for agent-to-agent communication, always inside an isolated SubAgent. Use when running coding…
Delegates a self-contained task to a Google Gemini Managed Agent (Antigravity) running in a remote sandbox with code execution,…
Runs a deep-research query on Google Gemini's deep-research managed agent and returns a cited report. This skill should be used…
This skill should be used when the user asks to "understand a codebase", "get code context", "research a library", "explore a…
Execute this when the user requests code context for a repository, library, or any natural-language code/technology question…