Technical Writing

Expert guide for writing successful research funding proposals for biological sciences. Specialized focus on NIH grants, biomedical research funding, career development awards, and fellowship applications. Covers proposal structure, review criteria, budget planning, collaboration strategies, and biological research-specific considerations.

Use when user says "save this", "create project", "promote from inbox" - manages Obsidian vault documentation with frontmatter (project/status/type/created), file naming (YYYY-MM-DD-name.md), wikilinks, and project structure in projects/ folders

This skill should be used when enhancing FHIR meeting minutes by synthesizing transcript discussion into Confluence pages, capturing reasoning and trade-offs with XML DOM manipulation

Critical guardrail for Supabase database operations ensuring multi-tenant isolation with publication_id filtering, proper use of supabaseAdmin, avoiding SELECT *, error handling patterns, and secure server-side database access. Use when writing database queries, working with supabase, accessing newsletter_campaigns, articles, rss_posts, or any tenant-scoped data.

Guidelines for writing effective user stories with clear acceptance criteria. Use when creating issues from discovery findings.

Craft Substack newsletter posts optimized for engagement, open rates, and subscriber growth.Use when writing headlines/subject lines, structuring posts, crafting hooks, writing teasersfor next issues, or adapting content between newsletter and Notes. Includes email-firstoptimization, the cliff-hanger technique, SEO integration, and Spanish-language patterns.

Use when implementing a written plan — executes tasks in order and keeps docs and checklists in sync.

Use when releasing a new version, updating CHANGELOG.md, or user asks to document changes - enforces Keep a Changelog format with proper categorization derived from conventional commits

Read-only code exploration and documentation search agent

Write high-quality Zenn technical articles following Japanese article writing best practices, focusing on problem-solving narratives rather than technology showcases

Master Archivist - Documentation keeper, knowledge organizer, and institutional memory

Platform-specific patterns for iOS and Android. Use when writing platform-conditional code.

Validates tests for test theater anti-patterns. Use when reviewing test code, writing new tests, or when user asks to check tests for quality issues. Ensures tests verify real behavior, not just provide false confidence.

Use this skill when you are writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.

Use this skill when writing or updating SQL queries (query.sql) or Python ETL scripts (query.py) following Mozilla BigQuery ETL conventions. ALWAYS checks for and updates existing tests when modifying queries. Coordinates downstream updates to schemas and tests. Works with bigquery-etl-core, metadata-manager, and sql-test-generator skills.

Research accelerator portfolio companies using Firecrawl and Tavily MCPs. Generates structured CSV and markdown reports with systematic impact scoring. Optimized for token efficiency.

Creates beautiful ASCII art visualizations for plans, architectures, workflows, and data. This skill should be used when explaining system architecture, creating implementation plans, showing workflows, visualizing comparisons, or documenting file structures. NOT for code syntax highlighting or markdown tables. User explicitly loves ASCII art - use liberally for visual communication.

Creates design document infrastructure including templates, workflows, and a specific design doc skill. Use when setting up design docs for a new project or when the user mentions "bootstrapping-design-docs".

Run comprehensive code quality checks including TypeScript typecheck, ESLint linting, Prettier formatting, and Markdown validation. Auto-fixes formatting issues in agent mode or provides read-only checks for CI pipelines. Use when: (1) Before committing code changes, (2) In CI/CD pipelines for automated quality gates, (3) After making significant code changes, (4) When preparing code for review, (5) When ensuring code meets quality standards, (6) For type checking, linting, formatting, and markdown validation, (7) In pre-commit hooks, or (8) For automated quality gates before merging. Triggers: finalize, code quality, typecheck, lint, format, check code, quality check, run checks, pre-commit, before commit, CI checks, validate code.

Writing high quality Frontend React code with following best practices and conventions. Use this skill when user asks for creating new components, refactoring old components, bug fixing components. The mentioned conventions and best practices should be followed with respect to the project structure and purpose.