CtrlK
BlogDocsLog inGet started
Tessl Logo

chainlink-ace-skill

Handle Chainlink ACE (Automated Compliance Engine) work using the public smartcontractkit/chainlink-ace repository and official docs.chain.link ACE Platform docs. Use for audited ACE core contracts, managed Platform/Beta scope, Coordinator API, Reporting API, Policy Management, PolicyEngine, PolicyProtected, policy chains, custom policies, extractors, mappers, Cross-Chain Identity (CCIDs), credential registries, KYC/AML credentials, sanctions screening, regulated tokens, ERC-20 and ERC-3643 compliance token examples, upgrade guidance, and BUSL licensing. Trigger on any mention of ACE, Automated Compliance Engine, chainlink-ace, Chainlink compliance, policy enforcement, ERC-3643, or onchain compliance rules, even if the user does not explicitly say 'ACE'.

86

1.15x
Quality

Does it follow best practices?

Impact

80%

1.15x

Average score across 2 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable body with clear navigation to real one-level-deep references and explicit validation/feedback checkpoints for destructive onchain operations. Its main weakness is redundancy between the Progressive Disclosure and Routing sections.

Suggestions

Consolidate the 'Progressive Disclosure' and 'Routing' sections, which both describe when to read which reference file; keep one intent-to-file map and fold the OSS-vs-Platform decision logic into the other to remove duplication.

Trim overlap between the 'Public Repo Defaults' / 'Managed ACE Platform Defaults' sections and the Overview, which restate the same source-of-truth distinction.

DimensionReasoningScore

Conciseness

The body is mostly efficient directive prose without explaining concepts Claude already knows, but the 'Progressive Disclosure' and 'Routing' sections repeat much of the same file-routing logic and could be merged, so it could be tightened.

2 / 3

Actionability

Guidance is concrete and specific: named functions/APIs (PolicyEngine, runPolicy, extractors, mappers, Coordinator/Reporting API resource families Transactions/Policies/Targets/Identities), concrete commands (pnpm build/test/lint, curl -L fallback), and a copy-paste preflight approval template.

3 / 3

Workflow Clarity

Sequences are clear with explicit checkpoints: Routing orders the OSS-vs-Platform decision first, the Approval Protocol requires a preflight summary plus a second explicit confirmation before any onchain write, and Documentation Access provides a WebFetch -> curl -> report-failure feedback loop.

3 / 3

Progressive Disclosure

The 'Progressive Disclosure' section maps each user intent to a specific reference file, all 10 referenced files exist, references are one level deep (SKILL.md -> references/*.md -> external URLs, no nested .md chains), and it explicitly says 'Do not load reference files speculatively.'

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, provides explicit 'Use when/Trigger on' guidance, and is clearly distinguishable from other skills. It does not pad with fluff or over-claim.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities ("PolicyEngine, PolicyProtected, policy chains, custom policies, extractors, mappers, Cross-Chain Identity (CCIDs), credential registries, KYC/AML credentials, sanctions screening, regulated tokens, ERC-20 and ERC-3643 compliance token examples"), matching the anchor for listing multiple specific concrete actions rather than vague language.

3 / 3

Completeness

It answers both 'what' (the enumerated capabilities and source-of-truth repos) and 'when' with explicit trigger clauses ("Use for..." and "Trigger on any mention of..."), matching the top anchor.

3 / 3

Trigger Term Quality

"Trigger on any mention of ACE, Automated Compliance Engine, chainlink-ace, Chainlink compliance, policy enforcement, ERC-3643, or onchain compliance rules" gives good coverage of the natural terms a user would say, including the instruction to trigger even without an explicit 'ACE' mention.

3 / 3

Distinctiveness Conflict Risk

The niche is narrowly scoped to Chainlink ACE compliance with distinct triggers (ACE, ERC-3643, chainlink-ace, onchain compliance rules), making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
smartcontractkit/chainlink-agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.