Agent skill · paperclipai
prepare-mcp-integration
Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection. Use for new integration research and delivery; not for ad hoc connector coding that bypasses the playbooks.
What it needs
About 7k tokens when loaded.
What this skill does
Prepare MCP Integration Take an input link or vendor brief through two separate phases: a reviewable research PR in paperclip-content, then connector implementation in Paperclip App only after a human accepts the exact research revision and connection set. Preserve These Boundaries Treat paperclip-content/integrations/README.md as the research contract and paperclip-content/integrations/skills/integration-harness/SKILL.md as its entrypoint. Reference and run them; do not copy their schemas, templates, state machines, reconciliation rules, or internal gates into this skill. Treat paperclip/doc/connections/CONNECTOR-PLAYBOOK.md on the implementation target branch as the connector contract. Follow it end to end; do not substitute remembered behavior or the examples in this skill. Finish Phase A with a research-only PR. Do not create an App implementation branch, task, or code change before the research gate is accepted. Bind acceptance to one research PR head SHA and an explicit connection set. Acceptance does not cover later commits or additional connections. Create one Paperclip App PR per approved connection. Shared prerequisite infrastructure or broad playbook corrections may use separate prerequisite PRs; never combine distinct connections into one connector PR. Keep vendor credentials in approved secret storage. Never put secrets in briefs, catalog files, issue text, plans, fixtures, screenshots, logs, branch names, commits, or PRs. Default Connection Experience Request the broadest vendor permissions and scopes the connection can support by default. Operators should not have to predict every future tool they may need during setup. Enforce safe use after connection through Paperclip's action catalog, resource boundaries, ask-first policies, quarantine, and audit controls. Keep the default wizard limited to the minimum information needed to create a working connection: connection identity, authentication, and any unavoidable tenant or resource boundary. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/prepare-mcp-integration