Skip to content
cccskills
FreePublished on GitHub

reserve-research

Research stablecoin reserve composition, review provenance, custody evidence, dependency edges, and backing-pillar slices; populate the owning reserves sidecar only when explicitly requested.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.2 KB
  • agents/openai.yaml237 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Read docs/editorial-style.md; its technical-evidence register governs prose.

Reserve Research

Read the current methodology version, docs/process/stablecoin-research-sidecars.md, docs/report-cards.md, the coin’s base/merged entry, and its reserves sidecar. shared/lib/stablecoins/schema.ts and shared/types/reserves.ts own shapes/tolerances. Research does not authorize mutations. When implementation is explicitly approved, write reserves, reserveReview, and custodyProfile only to shared/data/stablecoins/domains/reserves/<id>.json; create it when absent.

For pinned RPC reads and provenance, follow Pinned On-Chain Evidence.

Workflow

  1. Inventory collateral, peg mechanism, backing/governance flags, proof configuration, existing reserve slices/review, and custody profile. Preserve non-reserve fields unless explicitly in scope.
  2. Gather primary evidence: transparency dashboards, attestations, issuer/protocol docs, legal filings/fund facts, and protocol dashboards. Use secondary sources only to fill or corroborate gaps.
  3. Convert credible findings into concrete slices totaling 100 within the source-owned tolerance. Do not fabricate percentages.
  4. Populate current backing fields from evidence: assetClass, issuerOrObligor, liquidityHorizon, riskFactors, and maturityDaysMax only for a stated hard maximum—never convert weighted-average maturity. Link tracked stablecoin backing with coinId and justified depType.
  5. Keep schema-required legacy risk accurate using shared/lib/reserve-asset-risk.ts; for an unlisted symbol, choose the more conservative defensible tier and explain uncertainty. The current backing pillar uses structured slice fields, not this legacy tier.
  6. Author/refresh reserveReview with sources, basis/date, reviewed scope, reviewer/date/confidence, and required dispositions. Add custodyProfile only when its provider/control claims are evidenced.

For research-only work, present proposed JSON, sources, retrieval/observation times, basis date, approximations, reviewed gaps, and confidence without applying or generating data. For an addition, return the reserve portion of the addition/evidence handoff packet, including authorized fields/owner and proposed versus changed source paths.

For approved implementation, patch only the authorized sidecar fields. In coordinated work, return the packet and leave shared generation/catalog checks to the addition orchestrator after all specialists land. For a standalone approved edit, own the applicable Phase 7 generation/check pass after source edits are complete. Report observed versus unexercised verification in either mode.

Keep slice names specific; unknown structure remains explicit. A slice without assetClass or coinId is bounded unknown, not safe. A one-coin data update is not a methodology change.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review the retained annotation candidate queue and curate per-coin editorial history. Use weekly during active event periods, monthly otherwise, or on queue-health warnings; this does not restore the retired live chart overlay.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

Research and populate tracked stablecoin compliance sidecars for the U.S. GENIUS Act, EU MiCA, or both. Use when adding or auditing authorization, applicability, pathway, or disclosure evidence.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

Drain the Pharos Dependency Map coverage-audit queues into evidence-refreshed edges, reviewed target dispositions, or documented deferrals. Use monthly after weekly production dependency audits, after dependency coverage drops, or when reviewing adapter gaps, material unlinked slices, symbol leads, duplicate/split groups, or unverifiable published edges.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.

The English summary is being prepared. Showing the original description.

TokenBrice/pharos-watch24Updated Oct 21, 2026

See all skills by TokenBrice

Report a problem with this skill