Loading...
Loading...
Found 2,096 Skills
Manage Blink documentation and blog articles via the Blink MCP. Create, edit, publish, and version control MDX content on blink.new. Use when the user asks to update docs, write blog posts, or manage content on Blink.
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.
[Utilities] Convert PDF files to Markdown. Use when extracting text from PDFs, creating editable documentation from PDF reports, or converting PDF content to version-controlled markdown files.
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.
Bootstrap, maintain, and evolve context networks across their full lifecycle. Use when starting a new project, when existing documentation feels scattered, or when agent effectiveness degrades due to missing context.
Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.
Programmatic screenshot capture on macOS. Find window IDs with Swift CGWindowListCopyWindowInfo, control application windows via AppleScript (zoom, scroll, select), and capture with screencapture. Use when automating screenshots, capturing application windows for documentation, or building multi-shot visual workflows.
Creates Loop Page documents following company SOP standards. Use when user wants to create a new Loop page, meeting record, project document, or any documentation following company's Loop workspace conventions. Triggers on keywords like "Loop", "SOP", "create document", "meeting record", "project doc", or when user needs team documentation.
Gate Exchange welfare center new user task skill with MCP tools integration. Use this skill whenever user asks about welfare benefits, new user rewards, how to claim rewards, or available tasks. Trigger phrases include: what welfare, how to claim rewards, new user benefits, new user tasks, what tasks can I do, claim reward. CRITICAL: Must use real MCP data, never provide fake reward information. All documentation in English.
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.
Generate architectural wikis with source code traceability. Creates comprehensive documentation including architecture overviews, module docs, data flow diagrams, and interactive static sites. Use when asked to document a codebase, generate architecture docs, create a wiki, or explain how a project is structured.
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes