AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

External Integration Adequacy

skill-evolplus-talos-external-integration-adequacy · by evolplus

SA pre-sign-off procedure for validating and completing docs/external-integrations/<system-slug>.md placeholders. Use when Solution Architect is dispatched in `external-integration-adequacy` mode to fill operations, authentication, NFR posture, failure modes, regional/compliance constraints, adequacy issues, and to set Adequacy: adequate only when complete.

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-evolplus-talos-external-integration-adequacy

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-evolplus-talos-external-integration-adequacy)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of External Integration Adequacy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

External Integration Adequacy

Use

Use this skill when BA Phase 1.X created integration placeholders and the Orchestrator dispatches SA in external-integration-adequacy mode. This runs before SRS sign-off.

Inputs

  • Placeholder files under docs/external-integrations/.md
  • Linked US/FR files for each placeholder
  • SRS §3.5 integration index
  • solution-defaults for in-org default systems
  • Vendor/in-org interface docs named by Source-URL

Outputs

  • Updated external-integration files
  • Mirrored SRS §3.5 Adequacy values only when needed
  • Worktree plan-update.json summarizing adequate vs inadequate systems

Procedure

For each placeholder:

  1. Read header metadata, linked US/FRs, owner/source fields, and existing §7 gaps.
  2. Pre-fill from solution-defaults when available, then fill product-specific details from source docs.
  3. Fill §2 Operations, one subsection per operation:
  • endpoint/topic/RPC, protocol, direction, auth mode, idempotency;
  • request/response schemas, success and error variants;
  • vendor error code -> meaning -> product handling -> local error envelope;
  • rate limit, latency/SLO, retry policy, webhook/callback details.
  1. Fill §3 Authentication & Authorization.
  2. Fill §4 Non-Functional Posture.
  3. Fill §5 Failure Modes.
  4. Fill §6 Regional / Compliance when applicable.
  5. Record every missing source-backed field in §7 Open Adequacy Issues.
  6. Set Adequacy: adequate only when every operation is complete and §7 is empty; otherwise set inadequate.
  7. Stamp validation metadata and changelog.
  8. Mirror the SRS §3.5 Adequacy column to match the file header. Do not edit any other SRS body content.
  9. Commit, then emit plan-update.json.

Hard Rules

  • SA is the only role permitted to set Adequacy: adequate.
  • Never set Adequacy: deferred.
  • Never invent vendor/interface details.
  • Never leave TODO markers without matching §7 gaps.
  • Keep files self-contained; body sections must not say see .
  • Do not discover/propose new dependencies in this mode.
  • Commit before signaling done.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.