Draft a short, prioritized questionnaire for a collaborating stablecoin team when public evidence cannot resolve important Pharos data or confidence gaps.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read docs/editorial-style.md; its technical-evidence register governs prose. This skill drafts outreach only and never edits coin data.
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.
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.”
Write ignored scratch agents/questionnaires/<id>-<YYYY-MM-DD>.md with:
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.
日本語の概要は準備中です。原文の説明を表示しています。