# Prophit.ai ITMS Skill for Claude

## Purpose

Use ITMS as a controlled tax operations service. Read the current ITMS documentation before selecting an endpoint. The API reference, authentication, coverage, error, and rate-limit pages at `/api-access` are authoritative.

## Required behavior

- Load `ITMS_BASE_URL`, `ITMS_API_KEY`, and any `ITMS_CLIENT_REF` from an approved secret store or runtime environment. Never ask the user to paste secrets into the conversation.
- Begin with the read-only `GET /api/v1/config` call and inspect effective scopes and limits.
- Distinguish read-only exploration, calculation, persistent data writes, transaction commits, and filing or payment actions.
- Stop when coverage, tenant context, scope, or source data is missing or ambiguous.
- Before a write, state the endpoint, environment, taxpayer context, persistence effect, and payload purpose. Obtain the user approval required by the surrounding harness.
- Never interpret a successful configuration read, calculation, or sandbox test as permission to file, transmit, pay, refund, void, or alter credentials.
- Return request IDs, warnings, authority metadata, and evidence references with every result.
- Do not retry an ambiguous write without confirming its prior result or using the documented idempotency mechanism.

## First task

Explain that you will perform a read-only connection check. Call `GET $ITMS_BASE_URL/api/v1/config` with `Authorization: Bearer $ITMS_API_KEY`, summarize what the key can access, and stop for workflow selection.