agentsclimarketplace

Api integration builder

Skill intelligems-io/intelligems-mcp-skills/skills/api-integration-builder

Ready-to-install Agent Skills for analyzing Intelligems experiments, segments, pricing, and reporting through MCP and API.

Install
npx -y skills add intelligems-io/intelligems-mcp-skills --skill api-integration-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a user wants to build scripts, dashboards, alerts, or data pipelines with the Intelligems External API and needs source-backed endpoint guidance.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, 331 tokens by cl100k_base, as published. Nobody here has run it

API Integration Builder

Use this skill when building or reviewing code that calls the Intelligems External API.

First Moves

  1. Load references/external-api.md.
  2. Confirm the integration goal: reporting, monitoring, dashboarding, lifecycle automation, or data export.
  3. Confirm whether the task is read-only. Creating, updating, starting, pausing, or ending experiences requires explicit user approval.
  4. Use INTELLIGEMS_ACCESS_TOKEN or another environment variable. Never hardcode tokens.

Request Pattern

Base URL:

https://api.intelligems.io

Header:

intelligems-access-token: $INTELLIGEMS_ACCESS_TOKEN

Implementation Rules

  • Read the OpenAPI spec when endpoint shape matters.
  • Handle 400, 401, 404, 429, and 500.
  • Respect rate-limit headers: x-ratelimit-limit, x-ratelimit-remaining, and x-ratelimit-reset.
  • Prefer typed clients or schema validation for production integrations.
  • Keep raw API responses out of tracked files unless anonymized.
  • Log request IDs, endpoint names, and high-level status, not tokens or private payloads.
  • Treat export URLs, generated graphs, raw JSON, order-level CSVs, and line-item CSVs as private data.

Output For Code Tasks

When producing code, include:

  1. Environment variables required.
  2. Endpoint list used.
  3. Error handling.
  4. Rate-limit handling.
  5. Validation or test plan.
  6. Safety note for any mutating endpoint.

Gives 0 of the 12 instructions most apis services skills give in 331 tokens

Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06

  • use plural nouns for resource namesin 41 of 424, across 32 files
  • use cursor-based pagination for large datasetsin 35 of 424, across 20 files
  • include rate limit headers in responsesin 25 of 424, across 13 files
  • Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
  • version APIs in the URL pathin 19 of 424, across 9 files
  • use semantic HTTP status codesin 18 of 424, across 8 files
  • verify webhook signaturesin 18 of 424, across 11 files
  • use query parameters for filteringin 17 of 424, across 6 files
  • use async database operationsin 14 of 424, across 7 files
  • wrap successful responses in a data fieldin 13 of 424, across 3 files
  • prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
  • set appropriate HTTP status codesin 13 of 424, across 6 files

Said here and by no other author read

  • load the external api reference
  • confirm the integration goal
  • confirm whether the task is read-only
  • require explicit approval for mutating endpoints
  • handle 400, 401, 404, 429, and 500 errors
  • prefer typed clients or schema validation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.