Loading...
Loading...
Found 9 Skills
Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
Comprehensive reference for building Mintlify documentation sites. Use when creating pages, configuring docs.json, adding components, setting up navigation, or working with API references. Routes to detailed reference files for all components and configuration options.
Comprehensive guide for writing and updating Prefect documentation. Use when creating new doc pages, updating existing docs, or working with Mintlify components and code example testing.
Write and revamp product documentation to a high editorial standard using Mintlify, with strong information architecture, precise titles/descriptions, parameter-level clarity, cross-linking, and maintainable examples. Use when creating new docs pages, refactoring existing docs, improving docs structure/navigation, or standardizing docs quality across a repository.
Read and navigate external documentation efficiently. Invoke when the task requires checking how a specific function, endpoint, or configuration option works; when the user references an API, SDK, library, or third-party tool by name; when any docs URL or documentation site is mentioned; or when implementing something that depends on an external service or package.
Migrate an existing documentation site (Mintlify, Docusaurus, Fumadocs, Nextra, Starlight, or any docs framework) to Blume, the markdown-first docs framework on Astro. Translate the source config to blume.config.ts, restructure content into Blume's filesystem-derived navigation, rewrite JSX callouts to directives, convert icons to Lucide, and inline snippets. Use when the user asks to migrate/convert/port a docs repo to Blume, or when the repo has a docs.json/mint.json, docusaurus.config.*, meta.json with fumadocs, _meta.* with nextra, or an astro.config.* with starlight().
Style guide for all prose authored in this repo: mintlify docs pages, OpenAPI field and endpoint descriptions, changelog entries, READMEs, PR descriptions, PR review comments, and commit messages. Read BEFORE drafting, not after. Based on the Google developer documentation style guide (developers.google.com/style). Triggers: writing or editing any .mdx page, schema description, guide, PR description, or review comment.
Use this skill whenever the user is building against the Dealroom API OR asking you to look up Dealroom data conversationally (the next-gen REST API at api.beta.dealroom.app) - querying companies, startups, investors, funds, founders, people, funding rounds, valuations, news, jobs, or any Dealroom data. Triggers on "I have a Dealroom API key", "query the Dealroom API", "fetch startups", "build a server-side VC/scouting dashboard", "funding analytics", and on one-off conversational lookups like "show me X from Dealroom", "top startups in <sector/region>", "who invested in <company>", "how much has <company> raised", or any project that calls api.dealroom.app / api.beta.dealroom.app (or the retired api-next.dealroom.co / api-next.beta.dealroom.co hosts). Walks the user through Programmatic (M2M) API-key generation, sets up the OAuth2 client-credentials flow with automatic token refresh, picks the right endpoint for the question (transactional vs aggregate), and routes to the live OpenAPI spec and Mintlify docs. If the user mentions investors, fundings, startup ecosystems, scouting, VC data, unicorns, valuations, or the Dealroom platform, check whether this skill applies first.
Implements agent-readiness on public sites and docs from Mintlify Agent Score, AFDocs, Is Agentic, Is It Agent Ready, or url-discovery-bench reports, or from server logs of agents 404ing on guessed URLs. Use when asked to "make our site agent-ready", "improve Agent Score", "fix llms.txt coverage", "agents keep 404ing on our docs", or when a pasted scorecard is the brief.