Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
attestation-chain-auditor
Helps validate the completeness and integrity of trust attestation chains in AI agent ecosystems. Identifies broken links, expired credentials, and missing v...
skill openclawclawhub Free
Helps validate the completeness and integrity of trust attestation chains in AI agent ecosystems. Identifies broken links, expired credentials, and missing v...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- andyxinweiminicloud
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
The Chain Is Only as Strong as Its Weakest Link β Including the Links Nobody Checked
Helps identify gaps, breaks, and expired segments in trust attestation chains that make verification claims formally valid but practically meaningless.
Problem
Trust in agent ecosystems is supposed to be transitive: if A vouches for B, and B vouches for C, then A's trust extends to C through the chain. But attestation chains have failure modes that isolated audits don't catch. A chain can be formally complete β every link present β but functionally broken if any link is expired, if the vouching relationship was never actually verified, or if the chain contains circular dependencies that provide the appearance of independent validation without the substance. Many "verified" badges in current marketplaces represent attestation chains that would fail integrity checks if anyone looked at the full chain rather than just the terminal credential.
What This Audits
This auditor examines attestation chains across five dimensions: Chain completeness β Does a verifiable chain exist from the skill or agent all the way to a root of trust? Chains that terminate at unverified accounts rather than verifiable root authorities have a trust ceiling determined by their weakest link Link expiry β Are all links in the chain currently valid? An attestation signed 18 months ago with no renewal attests to a state that no longer exists. Each link should have a defined validity period and an explicit renewal or decay mechanism Vouching depth β How many independent vouching relationships exist? A chain where A vouches for B and B is also controlled by A (circular reference) provides zero independent validation despite appearing to have two links Authority legitimacy β Is each vouching authority in the chain itself attested by a higher authority? Self-signed roots are weaker than roots that are themselves attested by independent parties Revocation propagation β If any link in the chain is revoked, does that revocation propagate to all downstream attestations? A chain where link 2 has been revoked but links 3 and 4 don't know about it continues to appear valid to anyone who doesn't check the full chain
How to Use
Input: Provide one of: A skill or agent identifier to trace its attestation chain An attestation chain document to audit directly A list of vouching relationships to analyze for completeness and cycles Output: An attestation chain report containing: Chain visualization from skill/agent to root of trust Link-by-link validity assessment (active/expired/unknown) Circular dependency detection results Authority legitimacy assessment for each vouching node Revocation check results for all links Chain strength rating: STRONG / ADEQUATE / FRAGILE / BROKEN
Example
Input: Audit attestation chain for financial-data-processor skill π ATTESTATION CHAIN AUDIT Skill: financial-data-processor Published by: datatools-org Chain depth: 3 Chain visualization: financial-data-processor β vouched by: datatools-org (publisher account) β vouched by: marketplace-verified badge β vouched by: marketplace-platform (root) Link 1 β Skill β Publisher: Status: β οΈ PARTIAL Publisher signature: Present (RSA-2048) Signature date: 14 months ago Renewal: None found β attestation age exceeds recommended 12-month threshold Key transparency: β Not configured Link 2 β Publisher β Marketplace Badge: Status: β ACTIVE Verification type: Email verification + ID check Last verified: 3 months ago Renewal policy: Annual Link 3 β Badge β Marketplace Root: Status: β ACTIVE Root authority: marketplace-platform Root attestation: Self-signed Independent attestation: β None found β root is self-attesting Circular dependency check: β No cycles detected Authority legitimacy: marketplace-platform: Self-attesting root β no independent authority validates it Risk: Trust in the entire chain is bounded by trust in the platform itself Revocation check: Link 1 signing key: No revocation mechanism configured Link 2 (marketplace badge): Revocation via platform API confirmed Link 3 (root): N/A Chain strength rating: FRAGILE Reasons: 1. Link 1 attestation is 14 months old with no renewal 2. Root of trust is self-attesting with no independent validation 3. Link 1 has no revocation mechanism Recommended actions: 1. Renew publisher signature for financial-data-processor 2. Configure key revocation endpoint for publisher signing key 3. Seek independent attestation for marketplace root (third-party auditor)
Related Tools
publisher-identity-verifier β Checks publisher identity integrity; attestation chain auditor checks the full chain above the publisher trust-decay-monitor β Tracks trust freshness; use together to identify chains where time-based decay has weakened link validity agent-card-signing-auditor β Audits A2A Agent Card signing; attestation chain auditor checks what that signing is anchored to hollow-validation-checker β Detects validation theater; attestation chain auditor detects attestation theater
Limitations
Attestation chain auditing depends on the availability of chain metadata, which many current implementations do not publish. Where chain links are opaque or undocumented, this tool can identify that attestation information is missing but cannot reconstruct the chain. Self-attesting roots are common in current agent ecosystems β this tool flags them as weaker than independently-attested roots, but does not classify them as invalid. Chain strength ratings reflect the verifiability of trust claims, not the actual trustworthiness of the attested party β a strong chain attests to identity and history, not to benign intent.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md