cardputer-companion

Enforce physical confirmations and quiet notifications for Cardputer MCP tool usage.

197|20|Updated May 9, 2026
One-click install
npx skills add https://github.com/dakshaymehta/cardputer-claude-os --skill cardputer-companion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cardputer-companion
Source: https://github.com/dakshaymehta/cardputer-claude-os/tree/main/.claude/skills/cardputer-companion
Command: npx skills add https://github.com/dakshaymehta/cardputer-claude-os --skill cardputer-companion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents noisy, unsafe, or misleading interactions with the Cardputer MCP tools by enforcing a strict “confirm for irreversible actions” etiquette and quiet notification behavior.

Core Features & Use Cases

  • Mandatory physical confirmations: requires cardputer.confirm before irreversible operations and aborts on cancel/timeout/unavailable.
  • Quiet completion notifications: sends a single notify only when a task is genuinely long-running and completion is worth attention.
  • Smart asking when blocked: uses cardputer.ask only when you are blocked and the user may be away from the keyboard, with short choice-style questions.
  • LCD-friendly output formatting: keeps titles and message bodies compact for fast glance readability on the 240×135 display.
  • Do Not Disturb respect: avoids non-critical device chatter while still keeping destructive-op confirmations fail-closed.

Quick Start

Use the cardputer-companion skill to ensure that, when you run a potentially irreversible action like a force push, the AI calls the device confirm tool and stops if the device is unavailable.

Frequently Asked Questions about cardputer-companion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce physical confirmation for irreversible MCP tool actions?

To enforce physical confirmation for irreversible MCP tool actions, you need a fail-closed discipline that requires a physical device confirm before proceeding and aborts on cancel, timeout, or unavailability. This Skill applies that exact safety guardrail to Cardputer MCP interactions.

What is fail-closed device etiquette for BLE handheld alerts?

Fail-closed device etiquette for BLE handheld alerts is a runtime policy that mandates physical confirmation for destructive operations and suppresses non-critical chatter. It ensures potentially irreversible agent actions are safely blocked if the pocket device is unavailable or times out.

How do I format MCP notification messages for a 240x135 LCD display?

To format MCP notification messages for a 240x135 LCD display, keep titles and message bodies compact for fast glance readability. This Skill provides LCD-constrained formatting heuristics to ensure agent-driven alerts remain readable on the small Cardputer screen.

When should an AI agent use the ask tool for a blocked decision?

An AI agent should use the ask tool for a blocked decision only when the user may be away from the keyboard and needs to provide input. This Skill enforces smart asking behavior by limiting questions to short choice-style formats during genuine blockages.

Does this MCP safety guardrail respect Do Not Disturb policies for device notifications?

Yes, this MCP safety guardrail respects Do Not Disturb policies by avoiding non-critical device chatter while still keeping destructive operation confirmations fail-closed. It ensures quiet completion notifications are sent only for genuinely long-running tasks requiring attention.

What happens if the Cardputer device is unavailable during a force push confirmation?

If the Cardputer device is unavailable during a force push confirmation, the fail-closed protocol aborts the irreversible operation. This Skill prevents unsafe agent interactions by ensuring destructive actions cannot proceed without a successful physical confirm response.