-
Notifications
You must be signed in to change notification settings - Fork 0
chore: prune verified-dead core code (cli, sdk, resources, scripts) #409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
9021799
383a5fa
94649a6
5938182
480fd0e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| --- | ||
| name: sardis-audit | ||
| description: Teach an OpenClaw agent to inspect Sardis transactions, preserve evidence, and verify authority before reporting payment state. | ||
| homepage: https://sardis.sh | ||
| user-invocable: false | ||
| --- | ||
|
|
||
| # Sardis Audit | ||
|
|
||
| Use this skill only when `SARDIS_API_KEY` is present. If it is missing, state that Sardis audit data is unavailable. | ||
|
|
||
| ## Audit Flow | ||
|
|
||
| Use `sardis_list_transactions` to inspect the activity ledger before summarizing payment history, card activity, or budget usage. | ||
|
|
||
| Use `sardis_check_balance` before claiming available spend capacity. | ||
|
|
||
| Use `sardis_check_policy` before saying a future spend is allowed. | ||
|
|
||
| ## Reporting Rules | ||
|
|
||
| Report Sardis transaction identifiers, status, merchant, amount, currency, and evidence references when available. | ||
|
|
||
| Distinguish `pending`, `requires_approval`, `denied`, `settled`, and `revoked` states. | ||
|
|
||
| Never claim a payment completed from intent text alone. The ledger status is the source of truth. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| --- | ||
| name: sardis-payments | ||
| description: Teach an OpenClaw agent to use Sardis payment verbs with policy checks, reversibility awareness, and fail-closed handling. | ||
| homepage: https://sardis.sh | ||
| user-invocable: false | ||
| --- | ||
|
|
||
| # Sardis Payments | ||
|
|
||
| Use this skill only when `SARDIS_API_KEY` is present. If it is missing, do not create wallets, issue cards, or attempt payments. | ||
|
|
||
| ## Payment Verbs | ||
|
|
||
| Use `sardis_give_wallet` to provision the agent payment identity. | ||
|
|
||
| Use `sardis_spend` only after a successful `sardis_check_policy` result. | ||
|
|
||
| Use `sardis_pay_invoice` for invoice-shaped requests instead of manually constructing a payment when invoice metadata is available. | ||
|
|
||
| Use `sardis_issue_card` only when the user has explicitly requested a card and the policy result permits it. | ||
|
|
||
| Use `sardis_freeze_card` when a card is revoked, compromised, outside mandate, or no longer needed. | ||
|
|
||
| ## Fail-Closed Rules | ||
|
|
||
| If Sardis returns `requires_approval`, surface the approval requirement and wait. | ||
|
|
||
| If Sardis returns `deny`, stop the payment path. | ||
|
|
||
| If Sardis is unavailable, treat the action as denied until the service is reachable again. | ||
|
|
||
| Never expose raw card data, private keys, API keys, signing secrets, or provider tokens. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| --- | ||
| name: sardis-spending-policy | ||
| description: Teach an OpenClaw agent to set budgets, check policy before spend, and honor Sardis allow / requires_approval / deny outcomes. | ||
| homepage: https://sardis.sh | ||
| user-invocable: false | ||
| --- | ||
|
|
||
| # Sardis Spending Policy | ||
|
|
||
| Use this skill only when `SARDIS_API_KEY` is present. If it is missing, stop and ask the operator to configure Sardis before attempting any money movement. | ||
|
|
||
| ## Required Flow | ||
|
|
||
| 1. Create or update a budget with `sardis_set_budget` before the first spend. | ||
| 2. Run `sardis_check_policy` before every `sardis_spend`. | ||
| 3. Continue only when the policy result is `allow`. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The skill pack advertises that these instructions work with the Sardis MCP server (packages/sardis-openclaw/README.md lines 17-19), but this flow only permits spending when Useful? React with 👍 / 👎. |
||
| 4. Pause when the result is `requires_approval`. | ||
| 5. Refuse when the result is `deny`. | ||
|
|
||
| ## Guardrails | ||
|
|
||
| Never infer authority from user wording alone. The Sardis policy result is the authority boundary. | ||
|
|
||
| Never split one payment into smaller payments to bypass a budget, approval threshold, merchant block, token block, or time window. | ||
|
|
||
| Never retry a denied action with changed fields unless the operator explicitly changes the budget or mandate first. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The skill pack advertises that these instructions work with the Sardis MCP server (packages/sardis-openclaw/README.md lines 17-19), but this flow only permits spending when
sardis_check_policyreturns the literal agent-tools outcomeallow. The MCP implementation serializes policy results asallowed: true/falseanddecision.outcome: 'APPROVED' | 'BLOCKED'(packages/sardis-mcp-server/src/tools/policy.ts lines 64 and 412), so an OpenClaw agent using the supported MCP server will fail closed even for allowed payments because step 3 never matches. Include the MCP result shape, or scope the skill to agent-tools outcomes, before requiring the spend step.Useful? React with 👍 / 👎.