Install
$ agentstack add skill-batteryshark-skill-tap-mcp-elicitations ✓ 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
Build Interactive FastMCP Workflows
- Decide whether the interaction belongs in ordinary tool arguments, protocol elicitation, or an MCP App. Read [references/interaction-models.md](references/interaction-models.md).
- Use
ctx.elicit()for server-initiated, client-mediated structured input during a tool call. Define the response with supported scalar types or a Pydantic model and handle accept, decline, and cancel explicitly. - Use an action-only elicitation or the Apps Approval provider for a human checkpoint. A UI confirmation supplements server authorization; it never replaces it.
- Use
FastMCPAppor an app-enabled tool when the workflow needs an embedded form, choice, file upload, dashboard, table, or generative UI. Keep private app tools hidden from the model unless they independently belong in the model-facing catalog. - Keep credentials out of ordinary elicitation payloads when an OAuth or out-of-band authorization flow is appropriate.
- Run
bin/mcp-elicitations PATHto identify interaction code, then test accept, decline, cancel, invalid input, unsupported-client behavior, authorization failure, and replay/idempotency.
Use [agents/interaction-reviewer.md](agents/interaction-reviewer.md) to review trust boundaries and fallback behavior.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/skill-tap
- License: MIT
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.