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
—
Does it follow best practices?
Impact
80%
1.15xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
Policy chain ordering and terminal outcome explanation for ACE-protected ERC-20 transfer
Pause policy first
100%
100%
Reject/denylist before bypass
0%
0%
Size cap before bypass
0%
0%
Bypass policy last
0%
0%
Allowed skips remaining
100%
100%
PolicyRejected reverts
100%
100%
Continue passes through
100%
100%
BypassPolicy fast-path warning
70%
60%
Integration: inherit PolicyProtected
100%
100%
Integration: runPolicy on transfer
100%
100%
Integration: addPolicy attachment
100%
100%
OSS scope only
100%
100%
KYC credential design and validator for regulated DeFi lending
Custom namespace prefix
73%
100%
keccak256 form used
100%
100%
No PII onchain
100%
100%
PII alternative stated
100%
100%
CCID correlation risk mentioned
100%
100%
Multi-CCID privacy mitigation
100%
100%
Validator returns bool (no revert)
13%
100%
View function non-revert stated
0%
100%
Platform vs OSS distinction
0%
0%
Auditor evidence approach
100%
100%
6a60106
Table of Contents
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.