Install
$ agentstack add skill-evolplus-talos-external-integration-adequacy ✓ 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.
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
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-defaultsfor 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.jsonsummarizing adequate vs inadequate systems
Procedure
For each placeholder:
- Read header metadata, linked US/FRs, owner/source fields, and existing §7 gaps.
- Pre-fill from
solution-defaultswhen available, then fill product-specific details from source docs. - 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.
- Fill §3 Authentication & Authorization.
- Fill §4 Non-Functional Posture.
- Fill §5 Failure Modes.
- Fill §6 Regional / Compliance when applicable.
- Record every missing source-backed field in §7 Open Adequacy Issues.
- Set
Adequacy: adequateonly when every operation is complete and §7 is empty; otherwise setinadequate. - Stamp validation metadata and changelog.
- Mirror the SRS §3.5 Adequacy column to match the file header. Do not edit any other SRS body content.
- 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.
- Author: evolplus
- Source: evolplus/talos
- License: Apache-2.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.