تشغيل أي مهارة في Manus بنقرة واحدة

revertwtf-catalog-research

النجوم٤

التفرعات١

آخر تحديث٢٧ مايو ٢٠٢٦ في ١٣:٠٦

Perform broader source-backed catalog enrichment for new EVM ecosystems, protocols, providers, standards, or deprecated/renamed/sunsetting coverage.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

mrtdlgc

mrtdlgc/revertwtf

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	revertwtf-catalog-research
description	Perform broader source-backed catalog enrichment for new EVM ecosystems, protocols, providers, standards, or deprecated/renamed/sunsetting coverage.
version	0.1.0

revert.wtf Catalog Research Skill

Use this skill for broad catalog coverage passes: new chains, protocol ecosystems, contract repositories, provider APIs, standards, x402-style flows, explorer APIs, or lifecycle audits.

Research Standard

Prefer primary sources: official specs, protocol docs, contract repositories, API docs, EIPs/ERCs, release notes, and verified source repositories.
For current ecosystem status, verify live/current sources before marking something current, renamed, legacy, or sunsetting.
Keep historical coverage when old contracts can still emit errors. Mark it legacy; do not delete useful entries just because the product is deprecated.
Distinguish:
- legacy: deprecated, wound down, or historical but still useful.
- sunsetting: active enough to matter but tied to an announced shutdown date.
- renamed: ecosystem branding changed while errors remain relevant.

Workflow

Define the coverage target and scope.
Inventory current coverage:
- Search shards in packages/catalog/src/data/shards/.
- Check packages/catalog/src/sources.ts for lifecycle metadata.
- Check generated selectors in packages/selectors/src/generated.ts when custom errors are involved.
Gather source material and record references in entries or sources.ts.
For Solidity custom errors, prefer using scripts/enrich-new-ecosystem-shards.mjs when the target fits its model.
Hand-author protocol/provider/API entries when errors are not Solidity custom errors.
Regenerate catalog data, run validation, and run the duplicate audit.

Quality Bar

Entries should be integration-useful, not merely encyclopedic.
nextSteps should tell an app, wallet, support console, or agent what to do next.
Avoid "retry later" as a default. Be specific about when retry helps.
Avoid adding entries from random forum posts unless they are backed by code, docs, or repeated real-world artifacts.
Avoid massive false-positive substring patterns.

Verification

node scripts/build-catalog-data.mjs --generate --dist --check
node --experimental-strip-types scripts/validate-catalog.ts
node scripts/check-catalog-duplicates.mjs --fail-on=id,same-source-selector
node node_modules/typescript/bin/tsc -p packages/catalog/tsconfig.json --noEmit
node node_modules/typescript/bin/tsc -p packages/parser/tsconfig.json --noEmit

Useful smoke checks:

node --input-type=module -e "import { getCatalog } from './packages/catalog/dist/index.js'; console.log(getCatalog().length)"

If generated source files or dist JSON change, keep them synchronized with the shard source.

المزيد من هذا المستودع

نفس المستودع

revertwtf-catalog-error-enrichment

mrtdlgc/revertwtf

Run evidence-locked enrichment passes over existing revert.wtf catalog errors, preserving good entries while improving generic explanations, actions, references, and helper metadata.

2026-05-304

revertwtf-agent-api

mrtdlgc/revertwtf

Use revert.wtf safely from agents, tools, browsers, or integrations through bounded HTTP APIs, MCP tools, and lightweight package subpaths without downloading the full catalog into client bundles.

2026-05-274

revertwtf-catalog-entry

mrtdlgc/revertwtf

Add or update precise revert.wtf catalog entries, fixtures, source metadata, and matcher tests for one or a small set of EVM/RPC/provider/wallet/protocol errors.

2026-05-274

revertwtf-frontend-product-ui

mrtdlgc/revertwtf

Work on the revert.wtf Next.js frontend as a distinctive error-forensics product surface, not a generic SaaS or stock brutalist page.

2026-05-274

revertwtf-mcp-server

mrtdlgc/revertwtf

Maintain or use the read-only revert.wtf MCP server that exposes bounded catalog search, parser, selector lookup, AA explanations, x402 entries, and Blockscout registry tools to agents.

2026-05-274

revertwtf-parser-decoder

mrtdlgc/revertwtf

Modify or debug revert.wtf normalization, revert-data extraction, trace extraction, ABI decoding, catalog matching, selector lookup, or ERC-4337 decoding behavior.

2026-05-274

revert.wtf Catalog Research Skill

Use this skill for broad catalog coverage passes: new chains, protocol ecosystems, contract repositories, provider APIs, standards, x402-style flows, explorer APIs, or lifecycle audits.

Research Standard

Prefer primary sources: official specs, protocol docs, contract repositories, API docs, EIPs/ERCs, release notes, and verified source repositories.

For current ecosystem status, verify live/current sources before marking something current, renamed, legacy, or sunsetting.

Keep historical coverage when old contracts can still emit errors. Mark it legacy; do not delete useful entries just because the product is deprecated.

Distinguish:

legacy: deprecated, wound down, or historical but still useful.
sunsetting: active enough to matter but tied to an announced shutdown date.
renamed: ecosystem branding changed while errors remain relevant.

Workflow

Define the coverage target and scope.

Inventory current coverage:

Search shards in packages/catalog/src/data/shards/.
Check packages/catalog/src/sources.ts for lifecycle metadata.
Check generated selectors in packages/selectors/src/generated.ts when custom errors are involved.

Gather source material and record references in entries or sources.ts.

For Solidity custom errors, prefer using scripts/enrich-new-ecosystem-shards.mjs when the target fits its model.

Hand-author protocol/provider/API entries when errors are not Solidity custom errors.

Regenerate catalog data, run validation, and run the duplicate audit.

Quality Bar

Entries should be integration-useful, not merely encyclopedic.

nextSteps should tell an app, wallet, support console, or agent what to do next.

Avoid "retry later" as a default. Be specific about when retry helps.

Avoid adding entries from random forum posts unless they are backed by code, docs, or repeated real-world artifacts.

Avoid massive false-positive substring patterns.

Verification

node scripts/build-catalog-data.mjs --generate --dist --check node --experimental-strip-types scripts/validate-catalog.ts node scripts/check-catalog-duplicates.mjs --fail-on=id,same-source-selector node node_modules/typescript/bin/tsc -p packages/catalog/tsconfig.json --noEmit node node_modules/typescript/bin/tsc -p packages/parser/tsconfig.json --noEmit

Useful smoke checks:

node --input-type=module -e "import { getCatalog } from './packages/catalog/dist/index.js'; console.log(getCatalog().length)"

If generated source files or dist JSON change, keep them synchronized with the shard source.