integration-capabilities-sync

Fetch official API docs and update integration capabilities-and-scopes references.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Motion-Creative/runneth-apps --skill integration-capabilities-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-capabilities-sync
Source: https://github.com/Motion-Creative/runneth-apps/tree/main/integration-capabilities-library
Command: npx skills add https://github.com/Motion-Creative/runneth-apps --skill integration-capabilities-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents the agent from guessing what a connected integration can do and what permissions or scopes it needs by maintaining a sourced capabilities reference that stays current.

Core Features & Use Cases

  • New-integration documentation: Automatically fetches official API docs and generates a capabilities-and-scopes one-pager for newly detected integrations.
  • Nightly refresh & patching: Re-fetches documentation on a schedule, diffs changes, and updates only what changed so permissions and limits remain accurate.
  • Answer-time source of truth: Ensures integration capability questions are answered from the stored reference files rather than memory or inference.

Quick Start

Tell the agent to run the integration-capabilities-sync skill for the integration you just connected so it creates or updates the capabilities-and-scopes file from official documentation.

Frequently Asked Questions about integration-capabilities-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep integration capabilities and OAuth scopes accurate automatically?

Maintain integration capabilities and OAuth scopes accurately by fetching official API documentation on a schedule, diffing changes, and patching only what updated so permissions remain current without manual intervention.

What is the best way to document API scopes for newly connected integrations?

Document API scopes for new integrations by automatically fetching official web documentation to generate a sourced capabilities-and-scopes reference one-pager, ensuring permissions are recorded accurately from the start.

How does nightly sync detect API or scope changes in connected integrations?

Nightly sync detects API or scope changes by re-fetching official documentation on a schedule, diffing the new content against stored references, and applying patches to update only the modified capabilities or permissions.

Why does my agent guess integration permissions instead of using stored references?

Agents guess integration permissions when they lack a stored capabilities reference; using a sourced reference file ensures capability questions are answered from official documentation rather than memory or inference.

What happens to capability syncing when official API documentation cannot be located?

When official API documentation cannot be located during capability syncing, the system applies safe fallback behavior to preserve existing reference files and prevent overwriting accurate scopes with missing data.