# Build Auditable Data Asset Ledgers

Disconnected asset, finance, and rights records create reconciliation and audit gaps. This skill designs linked ledgers, asset cards, controls, and operating procedures.

## Install

```bash
npx skillstore add 图灵数盟/dhturing-data-asset-ledger-expert
```

## Metadata

- Status: approved
- Slug: dhturing-data-asset-ledger-expert
- Skillstore revision: r1
- Version status: missing
- Tree hash: 3b0c6becf90094a0b1a78076d27b684d3c22f0526e86bda9930bc1ad74da0628
- Author: 图灵数盟
- GitHub username: dhturing
- License: MIT
- Repository: https://github.com/dhturing/turing-data-experts/tree/9c58ffa97ec5b760befef6f910eb23107cdcdbf4/skills/data-asset-ledger-expert
- Ref: 50b73f83991cf073cbdf3f5afad2bbac71dd3bae
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dhturing-data-asset-ledger-expert
- Manifest: https://skillstore.pages.dev/api/skills/dhturing-data-asset-ledger-expert/manifest

## Capabilities

- Designs asset, finance, and rights ledgers with defined relationships.
- Creates data asset cards covering identity, ownership, technology, finance, security, and responsibility.
- Defines unique asset numbering rules and shared master data principles.
- Produces reconciliation and inventory workflows with documented review records.
- Structures annual impairment reviews around operational, technical, legal, and usage indicators.
- Drafts ledger governance procedures, quality checks, responsibilities, and handover controls.

## Use Cases

- Create a First Ledger: Turn an approved data asset list into linked ledgers, asset cards, numbering rules, and ownership fields.
- Resolve Ledger Differences: Analyze missing, retired, or differently classified assets and define a repeatable reconciliation process.
- Prepare Audit Evidence: Organize inventory records, responsibility assignments, amortization data, impairment reviews, and supporting evidence indexes.

## Prompt Templates

### Draft an Asset Card

```
Create a data asset card for [asset name]. Include identity, ownership, technical, financial, security, responsibility, and status fields.
```

### Design Three Ledgers

```
Design asset, finance, and rights ledgers for [organization]. Define shared identifiers, required fields, owners, update events, and reconciliation points.
```

### Investigate a Reconciliation Gap

```
Our asset ledger has [count] items, while finance has [count]. Classify likely causes and provide investigation steps, evidence needs, and controls.
```

### Build a Governance Program

```
Develop a governance program for [portfolio]. Include initialization, system integration, access control, quarterly reconciliation, inventory, impairment review, reporting, and handover.
```

## Limitations

- Does not connect directly to finance, registry, or data management systems.
- Cannot verify supplied ownership evidence, balances, valuations, or source records.
- Does not replace licensed accounting, valuation, audit, or legal advice.
- Policy references and timing recommendations require review against current local requirements.

## Best Practices

- Use one stable identifier across asset, finance, rights, and supporting systems.
- Keep evidence links, accountable owners, review dates, and approvals for every material change.
- Reconcile ledgers regularly and resolve differences through documented ownership and deadlines.

## Anti Patterns

- Do not create separate identifiers or uncontrolled copies for each system.
- Do not record values or ownership conclusions without supporting evidence and stated assumptions.
- Do not postpone inventory or impairment review until an audit request arrives.

## Security Audit

- Audited at: 2026-09-27T03:32:23.609\+00:00
- Summary: All 12 static findings are false positives. The home path is installation documentation, backticks are Markdown, URLs are author links, and entropy signals reflect plain Chinese prose. No prompt injection, covert execution, encoded payload, or data exfiltration intent was found.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0