App Integration Shaping
Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.
Install
$ agentstack add skill-45ck-skill-harness-app-integration-shaping ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-45ck-skill-harness-app-integration-shaping) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: 45ck
- Source: 45ck/skill-harness
- License: MIT
- Homepage: https://github.com/45ck/skill-harness/releases/tag/v0.1.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.