Claude Skills by FerroxLabs

Technical proposal writing expert covering proposal structure (problem, solution, approach, timeline, budget), executive summary, technical approach section, risk mitigation, competitive differentiation, pricing strategies, and review process. Use when the user asks about proposal writer, proposal writer best practices, or needs guidance on proposal writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Improves text readability by reducing complexity, shortening sentences, simplifying vocabulary, and restructuring for scan-ability. Targets a specific reading level or audience. Use when the user asks to make text more readable, reduce the reading level, simplify language, or make content accessible to a broader audience. Do NOT use for clarity of specific passages (use clarity-editing), conciseness without readability goals (use conciseness-editing), or academic writing conventions (use rese...

Expert README and project documentation covering README structure template, badges, installation instructions, quick start guide, configuration reference, contributing guide, license selection, architecture overview, and FAQ section. Use when the user asks about readme writer, readme writer best practices, or needs guidance on readme writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Creates GitHub-ready README.md files with project overview, installation instructions, usage examples, configuration details, and contributing guidelines. Use when the user needs a README for a repository, wants to improve an existing README, or asks for project documentation. Do NOT use for API documentation (use `api-documentation`), user guides (use `user-guide`), or changelogs (use `changelog-writing`).

Writes specific, evidence-based recommendation letters for academic, professional, and personal contexts with competency mapping, concrete examples, and credible endorsement structure. Use when the user asks to write a recommendation letter, reference letter, letter of support, or endorsement for a colleague, student, or acquaintance. Do NOT use for cover letters (use career skills), personal references for housing (different format), or self-recommendation (that is a personal statement).

Writes professional rejection letters for job candidates, proposals, vendor bids, and partnership requests that maintain goodwill while delivering a clear decision. Use when the user needs to decline an application, proposal, or request formally. Do NOT use for general business letters (use `business-letter`), conflict resolution emails (use `conflict-resolution-email`), or performance improvement plans (use `pip-writing`).

Creates version release notes categorized by change type (features, fixes, breaking changes) with migration guidance and user impact descriptions. Use when the user needs to write release notes for a software version, product update, or feature launch. Do NOT use for changelogs (use `changelog-writing`), technical specifications (use `technical-specification`), or status updates (use `status-update`).

Business report generation expert covering report structure, data visualization best practices, executive summary writing, metric presentation, trend analysis, recommendation formatting, appendix design, and automated report generation. Use when the user asks about report generator, report generator best practices, or needs guidance on report generator implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Expert guidance for communicating research findings to non-specialist audiences through press releases, lay summaries, conference presentations, media interviews, and public engagement strategies. Use when the user asks about research communicator, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of research communicator or requires a different specialized skill.

Structures research papers in IMRaD format (Introduction, Methods, Results, and Discussion) or social sciences format with section-by-section guidance, producing a complete paper framework. Use when the user asks to structure a research paper, write an academic paper, organize a study for publication, or create an IMRaD paper. Do NOT use for literature reviews (use literature-review), abstracts only (use abstract-writing), or editing an existing paper (use academic-paper-review).

Writes structured responses to Requests for Proposal (RFPs) with compliant formatting, clear capability statements, pricing structures, and persuasive differentiation for competitive procurement processes. Use when the user needs to respond to an RFP, RFI, or RFQ. Do NOT use for unsolicited business proposals (use `business-proposal`), internal project proposals (use `project-proposal`), or grant proposals (use `grant-proposal-writing`).

Expert operational runbook creation covering runbook structure, alert-to-runbook mapping, step-by-step procedures, escalation paths, rollback procedures, verification steps, communication templates, post-incident updates, and automation opportunities. Use when the user asks about runbook writer, runbook writer best practices, or needs guidance on runbook writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Writes satirical pieces that use irony, exaggeration, and absurdity to critique real-world subjects. Produces satire in various formats including mock articles, parodies, absurdist fiction, and satirical commentary. Use when the user asks to write satire, parody, mock articles, absurdist humor, or ironic commentary on a subject. Do NOT use for straight humor or comedy without a critical target (use writing-prompt-response), serious opinion pieces (use opinion-piece), or academic analysis of s...

Writes complete fiction scenes with setting, action, dialogue, and interiority that advance both plot and character. Integrates all craft elements into cohesive narrative units. Use when the user asks to write a scene, draft a chapter section, or create a narrative sequence with setting and action. Do NOT use for dialogue-only exchanges (use dialogue-writing), full short stories (use short-story-writing), or screenplay format (use screenplay-scene).

Producing science-focused podcasts from concept to publication, including expert interview techniques, episode scripting, fact-checking protocols, audio production workflow, and audience growth. Use when the user asks about science podcast producer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of science podcast producer or requires a different specialized skill.

Translating complex research findings for general audiences through clear narrative techniques, structured explanations, appropriate analogies, and publication strategies across media outlets. Use when the user asks about science writer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of science writer or requires a different specialized skill.

Expert guidance for creating educational science YouTube content covering scripting for clarity, data visualization, maintaining accuracy while being engaging, production techniques, and channel growth strategies. Use when the user asks about science youtube creator, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of science youtube creator or requires a different specialized skill.

Writes screenplay scenes in industry-standard format with slug lines, action lines, dialogue, and parentheticals. Enforces visual storytelling and proper screenplay conventions. Use when the user asks to write a screenplay scene, script a scene, format dialogue for screen, or draft in screenplay format. Do NOT use for prose fiction scenes (use scene-writing), stage plays (different format), dialogue-only exercises (use dialogue-writing), or full screenplay structure (use plot-outline for stru...

End-to-end self-publishing workflow covering KDP and IngramSpark, ebook and print formatting, ISBNs, pricing strategy, category and keyword optimization, cover design briefs, launch strategy, and royalty calculations. Use when the user asks about self publishing guide or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Writes SEO-optimized blog posts with strategic keyword placement, meta description, internal linking plan, and search-intent alignment. Use when the user wants a blog post designed to rank in search engines, asks for keyword- focused content, or needs organic traffic growth content. Do NOT use for general blog posts without SEO goals (use `blog-post-writing`), social media content (use `linkedin-post` or `twitter-thread`), or technical documentation (use `readme-writing`).

SEO content optimization expert covering keyword research, on-page SEO, meta description optimization, heading hierarchy, internal linking, technical SEO audit, structured data/schema markup, content freshness, and search intent matching. Use when the user asks about seo optimizer, seo optimizer best practices, or needs guidance on seo optimizer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Multi-book arc management covering character continuity, timeline tracking, escalation patterns, series bible construction, standalone versus sequential design, reading order strategy, and recurring element management. Use when the user asks about series planner or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Writes short stories (1,000-10,000 words) across any genre using constraint-first design and a five-step creative process. Collects genre, POV, premise, length, and one key constraint before drafting. Use when the user asks to write a short story, create fiction, draft a narrative, or develop a short prose piece. Do NOT use for flash fiction under 1,000 words (use flash-fiction), novel chapters (use plot-outline for planning), poetry (use poetry-writing), or screenplays (use screenplay-scene).

Tech social media content expert covering platform-specific formats (Twitter/X threads, LinkedIn posts, Dev.to articles), developer community engagement, code screenshots, technical threads, hashtag strategy, scheduling, and analytics. Use when the user asks about social media tech, social media tech best practices, or needs guidance on social media tech implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Creates standard operating procedures with step-by-step instructions, decision points, safety notes, and verification checks for repeatable processes. Use when the user needs to document a process, create a procedure manual, or write operational instructions. Do NOT use for how-to guides aimed at external audiences (use `how-to-guide`), project proposals (use `project-proposal`), or technical documentation (use a technical writing skill).

Professional speechwriting guide covering speech structure, rhetorical devices, audience analysis, delivery notes, occasion-specific approaches, and revision techniques for creating memorable and effective spoken presentations. Use when the user asks about speechwriter, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of speechwriter or requires a different specialized skill.

Writes executive-level stakeholder updates that translate project progress into business impact, surface decisions needed, and manage expectations for senior leadership audiences. Use when the user needs to update executives, board members, or cross-functional leadership on project or initiative status. Do NOT use for team-level status updates (use `status-update`), full business reports (use `business-report`), or board narratives (use `board-update-narrative`).

Writes structured status updates in accomplishments/upcoming/blockers format for weekly, sprint, or project reporting. Use when the user needs a status report, weekly update, sprint review, or progress report. Do NOT use for full business reports (use `business-report`), stakeholder updates for executives (use `stakeholder-update`), or meeting notes (use `meeting-notes`).

Creates compelling story pitches for novels, screenplays, TV series, and short fiction including loglines, synopses, comp titles, and query letter components. Use when the user asks to pitch a story, write a logline, create a query letter, draft a book synopsis, or prepare a pitch package for agents or producers. Do NOT use for business pitches or investor decks (use business pitch skills), full plot outlines (use plot-outline), or writing the actual story (use short-story-writing).

Narrative techniques for every professional context including business storytelling (Pixar framework, story spine), personal and brand narrative, data storytelling, presentation storytelling, emotional arc design, audience connection strategies, and building a personal story bank. Use when the user asks about storytelling master or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Performs structural (developmental) editing on documents, producing an editorial memo with assessment and a restructured outline showing proposed reorganization, reordering, and section changes. Use when the user asks for structural editing, developmental editing, document reorganization, or help with the overall structure and flow of a piece. Do NOT use for line-level editing (use copy-editing), proofreading (use proofreading), or tone changes (use tone-adjustment).

Checks and corrects text for compliance with a specific style guide (AP, Chicago, APA, MLA, or house style), producing a compliance report with every deviation identified and corrected. Use when the user asks to apply a style guide, check style compliance, format text to AP/Chicago/APA/MLA standards, or standardize document formatting. Do NOT use for general editing (use copy-editing), proofreading without a style guide focus (use proofreading), or citation-specific formatting (use citation-r...

Expert technical style guide creation covering tone and voice definition, terminology glossary, formatting standards, code sample conventions, inclusive language, abbreviation rules, numbering/list conventions, cross-reference patterns, and review checklist. Use when the user asks about style guide creator, style guide creator best practices, or needs guidance on style guide creator implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated te...

Creates technical deep-dive blog posts with code examples, architectural explanations, diagram descriptions, benchmarks, and lessons learned for developer audiences. Use when the user wants to write a technical blog post, engineering blog entry, or code walkthrough article. Do NOT use for general blog posts (use `blog-post-writing`), tutorials (use `tutorial-writing`), or API documentation (use `api-documentation`).

Engineering blog post creation covering article structure and narrative arc, technical explanation techniques, code example design, diagram creation, SEO optimization for developer content, editorial process, audience calibration, measuring post impact, and building a consistent publishing cadence. Use when the user asks about technical blog writer, technical blog writer best practices, or needs guidance on technical blog writer implementation. Do NOT use when the user needs a different speci...

Technical blog writing expert covering blog post structure, headline optimization, code example design, SEO for tech blogs, audience targeting, content calendar, distribution strategy, measuring engagement, and evergreen vs timely content. Use when the user asks about technical blogger, technical blogger best practices, or needs guidance on technical blogger implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Complete guide to writing and publishing technical books, covering publisher proposal development, code sample design, technical review processes, manuscript tooling including AsciiDoc and LaTeX, strategies for keeping content current, and royalty structure analysis. Use when the user asks about technical book author, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of technical book author or requires a different specializ...

Making complex topics accessible to any audience. Covers analogy creation, layered explanation (ELI5 to expert), visual communication strategies, the Feynman technique, jargon translation, audience assessment, FAQ design, and explainer formats (video, article, infographic) for technical communication. Use when the user asks about technical explainer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Technical presentation expert covering conference talk preparation, slide design for developer audiences, live coding demonstrations, demo preparation and backup plans, audience engagement techniques, storytelling for technical content, and talk proposal writing. Use when the user asks about technical presenter, technical presenter best practices, or needs guidance on technical presenter implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelat...

Expert guide to technical proposal writing covering RFP analysis, compliance matrices, technical approach narratives, past performance documentation, pricing strategies, and review processes for winning competitive government and commercial proposals. Use when the user asks about technical proposal writer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of technical proposal writer or requires a different specialized skill.

Creates technical specification documents with problem statement, requirements, design proposal, trade-off analysis, and decision rationale. Use when the user needs to write a tech spec, design document, or RFC for a proposed system or feature. Do NOT use for ADRs (use `adr-writing`), user guides (use `user-guide`), or API documentation (use `api-documentation`).

Crafts focused, arguable, specific thesis statements for academic papers, essays, and dissertations. Distinguishes between descriptive and argumentative thesis types and tests for strength. Use when the user asks to write a thesis statement, develop a central argument, or create the core claim for an academic paper or essay. Do NOT use for full paper structure (use research-paper-structure), abstract writing (use abstract-writing), or non-academic arguments (use different writing skills).

Adjusts the tone, register, and voice of written text while preserving meaning, producing before/after comparisons with tone markers showing every change and its rationale. Use when the user asks to change the tone, make text more formal or casual, adjust the voice, or shift the register of existing writing. Do NOT use for content-level editing (use copy-editing), structural changes (use structural-editing), or proofreading (use proofreading).

Complete guide to the traditional publishing path, covering query letters, agent research, book proposals, submission tracking, the publishing timeline, contract terms, working with editors, and understanding advances and royalties. Use when the user asks about traditional publishing or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Complete true crime writing guide covering research methodology, FOIA requests, interview techniques, ethical considerations, victim sensitivity, narrative structure, fact-checking protocols, and legal liability awareness. Use when the user asks about true crime writer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of true crime writer or requires a different specialized skill.

Expert technical tutorial creation covering tutorial structure (goal, prerequisites, steps, verification), progressive complexity, code sample design, screenshot guidelines, common mistakes section, prerequisite validation, and hands-on exercises. Use when the user asks about tutorial writer, tutorial writer best practices, or needs guidance on tutorial writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Creates learning-oriented tutorials with clear objectives, prerequisite knowledge, step-by-step instructions, explanations of why each step matters, and exercises for reinforcement. Use when the user needs to teach someone how to learn a skill or technology through guided practice. Do NOT use for task documentation (use `user-guide`), how-to articles (use `how-to-guide`), or API references (use `api-documentation`).

Writes numbered Twitter/X threads with a hook tweet, body tweets, and a closing CTA, all within character-count constraints. Use when the user wants to create a Twitter thread, X thread, or tweetstorm on a topic. Do NOT use for LinkedIn posts (use `linkedin-post`), blog posts (use `blog-post-writing`), or Instagram captions (use `instagram-caption`).

Creates task-oriented user guides with prerequisites, step-by-step procedures, expected outcomes, and troubleshooting sections. Use when the user needs documentation that teaches end users how to accomplish tasks with a product or system. Do NOT use for API reference docs (use `api-documentation`), developer tutorials (use `tutorial-writing`), or internal process docs (use `sop-writing`).

Creates brand voice and tone documentation with do/don't examples, vocabulary lists, platform-specific modifiers, and writing samples that any writer can follow to produce on-brand content. Use when the user needs to document their brand voice, create tone guidelines, build a writing style guide, or standardize how their brand communicates. Do NOT use for audience analysis (use `audience-analysis`), content strategy planning (use `editorial-calendar`), or actual content writing (use `blog-pos...