Explore skills

Use this skill when creating content strategy, writing SEO-optimized blog posts, planning content calendars, or repurposing content across channels. Triggers on blog strategy, content calendar, SEO content, content repurposing, editorial workflow, content pillars, topic clusters, and any task requiring content marketing planning or execution.

Google blog post introducing A2A protocol

Use this skill when writing headlines, landing page copy, CTAs, email subject lines, or persuasive content. Triggers on copywriting, headlines, landing pages, call to action, persuasion frameworks, AIDA, PAS, value propositions, and any task requiring compelling marketing or sales copy.

Use this skill when creating conference talks, live coding demos, technical blog posts, SDK quickstart examples, or community engagement strategies. It triggers on developer relations, DevRel, developer experience, tech evangelism, talk proposals, CFP submissions, demo scripts, tutorial writing, hackathon planning, community building, and any task involving advocating a product or API to a developer.

Use this skill for writing, reviewing, or improving internal engineering documents such as RFCs, design docs, and runbooks. It's ideal for drafting proposals, creating post-mortems, or enhancing existing documentation for clarity and completeness.

Generate a production-ready AbsolutelySkilled skill from GitHub repositories, documentation URLs, or domain topics. It triggers on commands like /skill-forge or 'create a skill for X', performing deep documentation research for URLs.

Sveltia CMS Git-backed content management (Decap/Netlify CMS successor). 5x smaller bundle (300 KB), GraphQL performance, solves 260+ issues. Use for static sites (Hugo, Jekyll, 11ty, Gatsby, Astro, Next.js), blogs, docs, i18n, or encountering OAuth errors, TOML/YAML issues, CORS problems, content listing errors.

Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads existing tech-spec as input. Use when: designing system architecture, documenting component interactions, creating architecture docs, producing 3-architecture.md. Not for: tech spec writing (use tech-spec), code implementation (use feature-dev)

Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.

Imports web pages as clean markdown using the local gather CLI. Use it to fetch URLs as markdown, clip pages into notes, archive readable articles, or convert web content for context.

After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.