Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

app-integration-shaping

Étoiles14

Forks1

Mis à jour11 avril 2026 à 02:03

Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

45ck

45ck/skill-harness

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	app-integration-shaping
description	Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.

Use this skill when deciding whether a new external integration belongs in the system and how it should be shaped.

Compare these options explicitly:

direct API client inside the application
separate service or worker
MCP server or connector-style integration
no integration yet because the problem is still underspecified

Checklist:

define the user or system workflow that needs the integration
identify data movement, ownership, and trust boundaries
specify required auth scopes and whether they are acceptable
call out rate limits, retries, partial failure, and observability needs
end with the recommended integration style and why it is the least-wrong option

Avoid:

defaulting to MCP because it is fashionable
burying auth scope risk inside implementation detail
merging integration design with product prioritization

Plus depuis ce dépôt

même dépôt

loop

45ck/skill-harness

Handle /loop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.

2026-06-2314

external-skill-fixture-builder

45ck/skill-harness

Turn external skill, rule, plugin, MCP, task-memory, and multi-agent workspace patterns into safe fixture coverage rather than live dependencies.

2026-06-1914

host-instruction-drift-checker

45ck/skill-harness

Check whether host instruction surfaces such as AGENTS.md, CLAUDE.md, Codex agents, Cursor rules, Copilot instructions, and SKILL.md files have drifted apart.

2026-06-1914

record-replay-skill-reviewer

45ck/skill-harness

Review skills generated from recorded workflows before they are installed, shared, or treated as reusable automation.

2026-06-1914

skill-provenance-reviewer

45ck/skill-harness

Review skills, agents, rules, plugins, and MCP/tool packs for license, source, script, permission, and supply-chain risk before adoption.

2026-06-1914

task-memory-profile-planner

45ck/skill-harness

Choose the right task-memory and issue-state pattern for a repo: Beads, lightweight files, external tracker integration, or no durable task memory yet.

2026-06-1914

name	app-integration-shaping
description	Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.

Use this skill when deciding whether a new external integration belongs in the system and how it should be shaped.

Compare these options explicitly:

direct API client inside the application
separate service or worker
MCP server or connector-style integration
no integration yet because the problem is still underspecified

Checklist:

define the user or system workflow that needs the integration
identify data movement, ownership, and trust boundaries
specify required auth scopes and whether they are acceptable
call out rate limits, retries, partial failure, and observability needs
end with the recommended integration style and why it is the least-wrong option

Avoid:

defaulting to MCP because it is fashionable
burying auth scope risk inside implementation detail
merging integration design with product prioritization