Total 50,315 skills, Documentation & Writing has 1449 skills
Showing 12 of 1449 skills
Use when responding to academic reviewers, planning revisions, writing rebuttals, mapping reviewer concerns, deciding concede/defend/reframe actions, or preparing camera-ready changes.
Use when building a state-of-the-art review, literature matrix, related work section, systematic search, paper comparison, gap analysis, or citation-backed synthesis.
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
Write conference papers (4-6 pages), poster abstracts, and prepare oral/poster presentations. Use when targeting conferences like NeurIPS, ICML, CVPR, ACL, IEEE venues, or preparing conference presentations.
Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.
Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in `apps/docs/content/releases/`.
Write scientific manuscripts. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), abstracts, for research papers and journal submissions.
Use this skill for writing, reviewing, and editing documentation (`/docs` directory or any .md file).
Generate lightweight section/subsection transitions (NO NEW FACTS) to prevent “island” subsections; outputs a transition map that merging/writing can weave in. **Trigger**: transition weaver, weave transitions, coherence, 过渡句, 承接句, 章节连贯性. **Use when**: `outline/subsection_briefs.jsonl` exists and you want coherent flow before/after drafting (typically Stage C5). **Skip if**: `outline/transitions.md` exists and is refined (no placeholders). **Network**: none. **Guardrail**: do not add new factual claims or citations; transitions may only refer to titles/RQs/bridge terms already present in briefs.
Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality
Enforces unified ID naming standards and threshold naming rules for all SDD documentation artifacts
This skill should be used when creating markdown-based presentations with expandable sections, timing guides, and speaker-friendly formatting. Use for team onboarding, technical deep-dives, and knowledge transfer sessions.