Skip to content
cccskills
FreePublished on GitHub

issuer-questionnaire

Draft a short, prioritized questionnaire for a collaborating stablecoin team when public evidence cannot resolve important Pharos data or confidence gaps.

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

See how to install

Files included (2)

  • SKILL.md2.9 KB
  • agents/openai.yaml289 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. This skill drafts outreach only and never edits coin data.

Issuer Questionnaire

Read the coin’s base file, all domain sidecars, current report card, shared/lib/methodology-versions/current-version.json, and shared/types/safety-score-v9-wrapper.ts. For keyed API access, check PHAROS_API_KEY in the ignored root .env.local without printing it.

Select Questions

Inventory scoreTrace.evidenceResponsibility.facts, pillar evidence/reasons, binding caps, weakest pillar, unknown access fields, NR reasons, and sidecar review gaps. Decode public fact paths with resolveEvidenceFactPath in shared/types/safety-score-v9-public-evidence-facts.ts. For reason routing, match the current typed gap-queue/replay entry and pass its structured path with reasonCode to descriptorForReason in scripts/lib/safety-score-v9-missing-data-work-types.ts; public path strings are not that argument, and missing-pillar-evidence cannot be routed by code alone. The Markdown curation worklist is a replay-derived summary, not the reason-routing authority. For bounded-mechanism-review facts, inspect only this coin’s entry in shared/data/safety-score-v9/mechanism-review-overlays-v1.json.

Ask about issuer-undisclosed facts or low-confidence facts that a document, policy, contract, or monitoring field can resolve. Ask about measured adverse exposure only as mitigation/recovery. Do not ask the issuer to solve producer failures, missing integrations, unsupported methods, or anything Pharos can verify from public sources, APIs, contracts, or explorers.

Rank critical facts first, then binding-cap/weakest-pillar/evidence-ceiling facts, high-weight weak-evidence facts, and useful confidence upgrades. Merge related gaps. Default to 4–6 neutral, non-leading questions; each must name the evidence that would settle it and accept “not currently defined.”

Deliverable

Write ignored scratch agents/questionnaires/<id>-<YYYY-MM-DD>.md with:

  1. Asset/team/date and key identifiers.
  2. Brief context on what Pharos already verifies and the public-evidence boundary.
  3. One section per direct question: verified adjacent facts, requested items, and mapped exact fact/reason code.
  4. One shared answer template: yes/no/not defined, explanation, URL or contract/function, effective date/block, change authority, and monitorable API/event.
  5. A close explaining that evidence enables re-review but guarantees no score/classification change.

After answers arrive, route generic identity/contracts to stablecoin-addition-orchestrator or stablecoin-identity-contracts, reserves to reserve-research, compliance to compliance-research, and resilience overrides to resilience-classify.

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 23, 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 23, 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 23, 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 23, 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 23, 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 23, 2026

See all skills by TokenBrice

Report a problem with this skill