mantle-data-indexer

Stars0

Forks0

UpdatedJune 14, 2026 at 03:42

Use when a Mantle task needs historical wallet activity, time-windowed metrics, event backfills, or protocol analytics that raw RPC cannot answer efficiently.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

mashharuki

mashharuki/Mantle-Repo

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name	mantle-data-indexer
description	Use when a Mantle task needs historical wallet activity, time-windowed metrics, event backfills, or protocol analytics that raw RPC cannot answer efficiently.

Mantle Data Indexer

Overview

Use GraphQL or SQL indexers to answer historical questions on Mantle with reproducible queries, clear time boundaries, and source attribution.

Workflow

Normalize request:
- objective (for example volume, swaps, user history)
- entities (wallet, pool, token, protocol)
- time range (absolute UTC start/end)
Resolve endpoint availability:
- mantle_querySubgraph requires endpoint + query.
- mantle_queryIndexerSql requires endpoint + query.
- If endpoint config is missing, request it explicitly instead of guessing.
- In E2E endpoint-configured scenarios, skip when E2E_SUBGRAPH_ENDPOINT or E2E_SQL_ENDPOINT is unset.
Select source by availability and latency target:
- GraphQL indexer -> mantle_querySubgraph
- SQL indexer -> mantle_queryIndexerSql
Build query from references/query-templates.md.
Execute with pagination and deterministic ordering.
Normalize units and decimals before aggregation.
Produce output with query provenance, tool warnings, and caveats.

Guardrails

Confirm chain scope is Mantle before querying.
Use absolute timestamps and include timezone (UTC).
Do not invent endpoint URLs. If missing, report blocked input and request an endpoint.
Keep SQL read-only; avoid mutation statements.
Do not merge datasets with mismatched granularity without labeling.
Distinguish no data from query failure.
Propagate tool warnings (for example hasNextPage=true or SQL truncation).
If indexer lag is known or suspected, disclose it.

Output Format

Mantle Historical Data Report
- objective:
- source_type: graphql | sql
- source_endpoint:
- queried_at_utc:
- time_range_utc:
- entity_scope:

Query Summary
- dataset_or_subgraph:
- filters_applied:
- pagination_strategy:
- records_scanned:

Results
- metric_1:
- metric_2:
- sample_rows:

Quality Notes
- indexer_lag_status:
- tool_warnings:
- assumptions:
- caveats:
- confidence:

References

references/indexer-selection-and-quality.md
references/query-templates.md

More from this repository

same repository

mantle-address-registry-navigator

mashharuki/Mantle-Repo

Use when a Mantle task needs a verified contract or token address, whitelist validation, anti-phishing checks, or safe registry-backed lookup before onchain interaction.

2026-06-140

mantle-defi-operator

mashharuki/Mantle-Repo

Use when a Mantle DeFi task needs discovery, venue comparison, or execution-ready planning with verified contracts, preflight evidence, and an external handoff.

2026-06-140

mantle-network-primer

mashharuki/Mantle-Repo

Use when users need Mantle fundamentals, developer onboarding context, or clarification of MNT gas, chain setup, inclusion, settlement, and finality.

2026-06-140

mantle-portfolio-analyst

mashharuki/Mantle-Repo

Use when a Mantle task needs wallet balances, token holdings, allowance exposure, or unlimited-approval review before a DeFi or security decision.

2026-06-140

mantle-readonly-debugger

mashharuki/Mantle-Repo

Use when Mantle read-path requests fail, quotes revert, balances disagree, or RPC behavior is inconsistent and needs structured root-cause triage.

2026-06-140

mantle-risk-evaluator

mashharuki/Mantle-Repo

Use when a Mantle state-changing intent needs pre-execution slippage, liquidity, address-safety, allowance-scope, or gas/deadline checks.

2026-06-140

Mantle Data Indexer

Overview

Use GraphQL or SQL indexers to answer historical questions on Mantle with reproducible queries, clear time boundaries, and source attribution.

Workflow

Normalize request:

objective (for example volume, swaps, user history)
entities (wallet, pool, token, protocol)
time range (absolute UTC start/end)

Resolve endpoint availability:

mantle_querySubgraph requires endpoint + query.
mantle_queryIndexerSql requires endpoint + query.
If endpoint config is missing, request it explicitly instead of guessing.
In E2E endpoint-configured scenarios, skip when E2E_SUBGRAPH_ENDPOINT or E2E_SQL_ENDPOINT is unset.

Select source by availability and latency target:

GraphQL indexer -> mantle_querySubgraph
SQL indexer -> mantle_queryIndexerSql

Build query from references/query-templates.md.

Execute with pagination and deterministic ordering.

Normalize units and decimals before aggregation.

Produce output with query provenance, tool warnings, and caveats.

Guardrails

Confirm chain scope is Mantle before querying.

Use absolute timestamps and include timezone (UTC).

Do not invent endpoint URLs. If missing, report blocked input and request an endpoint.

Keep SQL read-only; avoid mutation statements.

Do not merge datasets with mismatched granularity without labeling.

Distinguish no data from query failure.

Propagate tool warnings (for example hasNextPage=true or SQL truncation).

If indexer lag is known or suspected, disclose it.

Output Format

Mantle Historical Data Report - objective: - source_type: graphql | sql - source_endpoint: - queried_at_utc: - time_range_utc: - entity_scope: Query Summary - dataset_or_subgraph: - filters_applied: - pagination_strategy: - records_scanned: Results - metric_1: - metric_2: - sample_rows: Quality Notes - indexer_lag_status: - tool_warnings: - assumptions: - caveats: - confidence:

References

references/indexer-selection-and-quality.md

references/query-templates.md