agentleFS
codexceedcodexceed/avatar-harness/.agents/skills/mintlify-api/SKILL.md

mintlify-api

Skill1 starsChanged 5 months agoMITView on GitHub

Interact with the Mintlify REST API to manage deployments, trigger builds, and query documentation site metadata programmatically.

  • Commits and pushes

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the Mintlify API to manage documentation sites programmatically.

    line 13
  2. Very specific:

    All API requests require an API key passed in the Authorization header:

    line 17
  3. Distinctive:

    Create and manage preview deployments for pull requests and branches to review documentation changes before they go live.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mintlify API

Use the Mintlify API to manage documentation sites programmatically. This skill covers deployment management, build triggers, and site metadata queries.

Authentication

All API requests require an API key passed in the Authorization header:

Authorization: Bearer <your-api-key>

Generate API keys from the Mintlify dashboard under Settings > API Keys.

Core capabilities

Trigger deployments

Programmatically trigger a documentation rebuild when your codebase changes outside of Git push events.

Query site metadata

Retrieve information about your documentation site including deployment status, configured domains, and navigation structure.

Manage preview deployments

Create and manage preview deployments for pull requests and branches to review documentation changes before they go live.

Resources

Download now (ZIP)

Trending

Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 1 new projectWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.
  • Other versions4 projects use a version of this.

    Word for word · 4

    1. lampac-nextgen/lampac★ 361100% same
    2. jacred-fdb/jacred★ 128100% same
    3. immisterio/Lampac★ 77100% same
    4. 0mcpIO/docs★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use ponytail.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • GoogleSkill

      ponytail

      Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

      Also in 3 projects that use this

  • In this repository8 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.