All skills
payment-trading-extension
DomainJIT onlyFor analysis, task, or review agents using a Professional Skill on payments, trading, ledgers, settlement, refunds, or reconciliation; not for non-financial or Web3-only work.
- Routing mode
- modifier-only
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- payment
- ledger
- balance
- settlement
- trading
- order
- wallet
- money movement
Do not use when
Anti-triggers — as binding as the triggers above
- non-financial workflow with no monetary invariant
- price display or ordinary orders without funds, ledger, settlement, or execution state
Required inputs
What must be supplied before this skill can decide anything
- money representation, ownership, ledger, idempotency, reconciliation, and regulatory boundary
Output contract
What this skill owes the next role
- financial decision with invariant, authority, selected control, reconciliation limits, regulatory scope and accountable owner, control evidence, exceptions, release consequences, proof limits, and residual risk
Boundary signals
Signals that mark the edge of this skill's authority
- accounting
- reconciliation
- fill
- settlement
Escalation signals
When this skill must hand the decision back
- domain risk changes public behavior, irreversible state, safety, security, or financial correctness
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| financial-role-and-state-authority.mdtargeted | payment custody model, provider/custody/ledger/settlement roles, source of truth, or authoritative completion state is open | roles, source of truth, custody and authoritative state are already explicit, or no monetary state exists, including price display or ordinary orders without funds, ledger, settlement, or execution state | AnalysisTaskReview |
| raw-card-custody-evidence.mdevidence-pattern | approved raw-card custody requires PCI/PAN/CVV retention, storage, display, logging, or evidence closure | no raw-card custody exists; the flow is provider-hosted/non-custodial | AnalysisTaskReview |
| non-custodial-sensitive-data-boundary.mdtargeted | tokenized/provider-hosted payment flow must prove PAN/CVV/payment-secret exclusion | application has no reachable payment secret, or approved raw-card custody rather than a non-custodial boundary is being assessed | AnalysisTaskReview |
| duplicate-financial-effect-control.mdtargeted | retry, replay, concurrent submission, result reuse, or unknown outcome can repeat a financial effect | no retryable financial effect exists, or current provider/storage uniqueness is already proven and unchanged | AnalysisTaskReview |
| owned-financial-state-accounting-and-balances.mdtargeted | owned payment/ledger transitions, correction history, accounting ownership, or balance authority is open | pure provider orchestration owns no ledger, accounting book, or application balance | AnalysisTaskReview |
| trading-order-execution-and-identity.mdtargeted | order acknowledgement/fill/cancel/replace, execution identity, race, gap, or recovery behavior is open | payment-only work has no order execution, fill, cancel, venue identity, or trading-session recovery | AnalysisTaskReview |
| market-data-and-trading-risk-controls.mdtargeted | price-sensitive execution, risk limits, overrides, kill switch, leverage, margin, or liquidation behavior is open | no price-sensitive execution, leverage, override, limit, or kill-switch behavior changes | AnalysisTaskReview |
| venue-product-monetary-and-calendar-contracts.mdtargeted | venue/product units, tick/lot/notional, fee/funding, precision/rounding, currency, cutoff, calendar, or timestamp contract is open | no venue/product monetary representation or calendar contract changes, and current contracts are explicit | AnalysisTaskReview |
| provider-venue-event-authentication.mdtargeted | inbound provider/venue events require identity, replay, ordering, version, credential, or audit closure | no inbound external financial event is consumed | AnalysisTaskReview |
| financial-reconciliation-and-monitoring.mdtargeted | orders, executions, positions, balances, ledgers, settlements, corrections, breaks, replay windows, or operational signals require reconciliation closure | no cross-source reconciliation or financial-operability boundary changes | AnalysisTaskReview |