AGENT SKILL

testdino-audit

Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.

License 许可
Apache-2.0
最近更新
2026-11-12
Stars
★ 4.9k
Forks
363

01 前言 Front Matter

name
testdino-audit
description
Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.

03 SKILL.md 正文

TestDino Audit

Use the TestDino audit flow only when the user explicitly asks for a TestDino audit.

Rules:

  • If the user asks for a generic review or audit, do a normal review in chat.
  • If the user explicitly asks for a TestDino audit and the target is Playwright code, use the audit tools below.
  • If the user names TestDino but the target is not Playwright code, explain that the TestDino audit flow is for Playwright automated tests and offer a normal review instead.

Tool selection — use whichever audit tools the TestDino MCP server exposes:

  • If get_audit_report and submit_audit_report are available, prefer those (the current split tools).
  • If only the legacy test_audit tool is available, use it instead (it takes an action parameter).
  • Do not invent a tool that is not in the available tool list.

Preferred flow:

  1. Call health if projectId is not known.
  2. Fetch the audit context (read-only). Do not write findings, score, or headings before this returns.
    • New tools: get_audit_report with action: "context".
    • Legacy: test_audit with action: "analyze" and no score.
  3. Review the local Playwright target using the returned context and write findings to a local markdown file (e.g. TEST-AUDIT.md).
  4. Submit the completed report (score + markdown report).
    • New tools: submit_audit_report.
    • Legacy: test_audit with action: "analyze" plus score and markdownReport.
  5. Browse or retrieve previously submitted audits.
    • New tools: get_audit_report with action: "list" or action: "get".
    • Legacy: test_audit with action: "list" or action: "get".

Important:

  • keep generic reviews as normal chat reviews
  • use the TestDino audit flow only for explicit TestDino audit requests
  • keep this flow centered on Playwright automated test code

04 同仓库更多 Skills

anthropics
anthropics/claude-plugins-community

tres-wallets-upload

Upload and onboard multiple on-chain wallets or exchange accounts into Tres Finance. Use this skill whenever the user wants to add wallets, onboard wallets, import wallets, upload wallet addresses, ingest wallets, or connect exchanges into Tres — whether from a file (CSV/Excel) or by typing them manually. This skill guides Claude through the full flow: wallet type selection → input collection → validation → preview with editable HTML table → exchange credential collection (if exchange) → user confirmation → batch creation via the TRES MCP API. Always trigger this skill for wallet onboarding, wallet data ingestion, or any request to "add wallets to Tres".

财务电子表格Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

tres-upload-tx-header-validation

The exact column header names required by the TRES Finance bulk transaction CSV upload. Use whenever building, fixing, or validating the header row of a TRES manual transaction or sub-transaction upload CSV — especially after an upload fails with "Missing required column(s): ...". Trigger phrases include: 'fix my CSV headers', 'bulk transaction upload failed', 'missing required columns', 'validate TRES upload CSV', 'transaction CSV template headers'. This skill is ONLY about the header naming convention; it does not cover row values or upload workflow. Do NOT trigger for contacts import CSV (use tres-import-contacts), wallet upload CSV (use tres-wallets-upload), or general CSV parsing unrelated to bulk TX upload headers.

★ 4.9k
anthropics
anthropics/claude-plugins-community

tres-tx-story

Analyze a blockchain transaction by its hash using TRES Finance MCP and generate a visual flow diagram showing all asset movements, followed by a plain-language explanation of what happened. Use this skill whenever the user provides a transaction hash and asks to "analyze", "explain", "visualize", "diagram", "show me what happened in", or "tell the story of" a transaction. Also trigger when the user pastes a tx hash (long hex string starting with 0x) and asks anything about it. Always use this skill for transaction hash analysis — do not attempt to answer from memory alone.

Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

tres-settings-management

Manage Organization Settings and Platform Settings via the TRES MCP GraphQL API. Use when users ask about org settings, platform settings, configuration, feature flags, enable/disable platforms, balance diff, commit strategy, cost basis, ERP, pricing, sync boundaries, or any setting read/write operation. Trigger phrases include "get settings", "show settings", "update settings", "change settings", "enable platform", "disable platform", "balance diff", "commit strategy", "cost basis strategy", "set min sync date", "configure", "turn on", "turn off".

Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

tres-rollup-rules

Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on "create a rollup rule", "suggest rollup rules", "what should I roll up", "show my rollup rules", "delete a rollup rule", "aggregate transactions", "too many transactions", "reduce transaction count", "roll up fees", "daily rollup", "monthly rollup". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted/pending rules, use the tres-rollup-review skill instead.

财务Skill与智能体开发
★ 4.9k
anthropics
anthropics/claude-plugins-community

tres-rollup-review

Compute the EXACT sub-transaction impact of a rollup rule in TRES Finance — every filter applied — and flag genuine problems (zero matches, overlap, config mistakes) before the rule is created. Two modes. Mode A: a pre-create quality gate invoked by the tres-rollup-rules skill to vet proposed candidate rules. Mode B: standalone review of a rule someone submitted or of existing PENDING rules. Trigger this skill when the user says "review this rollup rule", "what would this rollup rule actually match", "preview the rollup impact", "how many transactions would this rule catch", "is this rollup rule valid", "validate my rollup rule", "check my pending rollup rules", or "review the rollup requests". Do NOT use this to design or propose new rollups — that is tres-rollup-rules. This skill only measures impact and flags issues; it never executes mutations.

财务Skill与智能体开发
★ 4.9k