Loading...
Loading...
Found 1,952 Skills
Review new or updated Coral source manifests and source PRs for content, style, product fit, query ergonomics, documentation quality, and consistency with existing Coral sources. Use when Codex is asked to review a sources/core/name or sources/community/name source directory, a manifest.yaml, or a GitHub PR that adds or changes a Coral source.
Scans any project repository and generates a "Source of Truth" documentation set in the core-knowledge folder, covering architecture, business logic, feature flags, deployment, and any cloud/serverless integrations.
Printing Press CLI for Jira Cloud Platform. Jira Cloud Platform REST API documentation
Systematic documentation authoring workflow for AI coding agents. Analyzes repositories to determine what documentation is needed, classifies each document by Diataxis type (tutorial, how-to, reference, explanation), and generates accurate, maintainable documentation that stays synchronized with the codebase. Handles greenfield projects (no docs exist), brownfield updates (refresh, enhance, rewrite existing docs), and doc audits with workflow-specific guidance for each. Use when the user requests documentation for a project: README creation, API reference, architecture docs, developer guides, changelogs, or any technical writing tied to a codebase. Also use when existing docs need auditing, updating, rewriting, or restructuring. Triggers on phrases like "write a README", "document this project", "API reference", "architecture doc", "developer guide", "getting started guide", "tutorial", "how-to", "audit our docs", "what docs are missing", "refresh the docs", "Diataxis", "doc the public API", "write a CHANGELOG", "explain this codebase", "onboarding doc", or "ADR". Triggers when creating or editing `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, `docs/`, `mkdocs.yml`, `docusaurus.config.*`, `sphinx`/`conf.py`, ADRs, or any markdown file paired with code. Triggers when public APIs, CLI flags, configuration options, or environment variables change and the user wants the docs kept in sync. Do NOT use for standalone prose, marketing copy, blog posts, design documents, RFCs unrelated to a codebase, or documents where the source of truth is not source code.
Creates selected backend Markdown documentation from code evidence, including architecture/design docs, bounded context maps, developer onboarding, API contracts, and gap analysis for code smells, project-rule violations, DDD issues, coupling, and improvement opportunities. Use when the user asks to document a backend, map backend architecture or domains, onboard backend developers, audit backend documentation gaps, or produce objective backend docs. Do NOT use for frontend docs, generic README writing, or implementing backend changes.
Guides the agent through creating and maintaining Capacitor plugins from scratch. Covers scaffolding a new plugin project, designing the TypeScript API, implementing native iOS (Swift) and Android (Java/Kotlin) bridges, implementing the web layer, defining TypeScript type definitions, plugin configuration values, plugin hooks, development workflow with local testing, documentation generation, and publishing to npm. Do not use for installing existing plugins into an app, upgrading existing plugins to newer Capacitor versions, adding SPM support to plugins, or non-Capacitor plugin frameworks.
Provides comprehensive code review covering 6 focused aspects - architecture & design, code quality, security & dependencies, performance & scalability, testing coverage, and documentation & API design. Use this skill for deep analysis with actionable feedback after significant code changes.
Post-change documentation sync for decisions, synthesis, skill maps, release notes, and durable handoffs.
You are a professional Customer Service Specialist and Communication Strategist. Use this skill when the user wants to write customer service scripts, support email templates, feedback responses, FAQ content, or help center articles. Activate when the user mentions "customer service," "support email," "support template," "help center," "knowledge base article," "FAQ for support," "chatbot script," "live chat script," "phone script," "customer feedback response," "review response," "refund email," "cancellation template," "late shipping response," "apology email," "product outage response," "billing email," "customer onboarding message," "troubleshooting guide," "password reset article," "support ticket," "macro," "saved reply," "customer service playbook," "internal support doc," "review reply," "3-star review," "negative review response," "positive review response," "customer loyalty message," "subscription cancellation script," "exchange template," "customer portal content," "chatbot flow," "in-app help copy," "social media response," "support documentation," or "customer service tone." Covers scripts for phone, chat, and messaging; email templates for all support scenarios; feedback and review responses; FAQ sections; and full help center articles with troubleshooting guides.
Research a vendor, product, or feature to collect all information needed before building an Elastic integration. Investigates data collection methods, API or log documentation, sample data formats, field schemas, ECS mapping candidates, and configuration requirements. Outputs a structured research brief to research_results/<product>/. Invoke manually with /research-integration.
Vast.ai API Documentation - Affordable GPU Cloud Marketplace
Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality