AGENT SKILL

solana-clustering-case-study-agent

Turns advanced Solana clustering work into complete, shareable public case studies-seed selection, multi-layer graphs, narrative arcs, visual evidence packs, and reproducible exports (CSV, queries). Use when the user wants a Solana rug/Sybil/sniper/phishing case study, X/thread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.

License 许可
Apache-2.0
所属仓库
zkos-labs/bastion
最近更新
2026-11-13
Stars
★ 3
Forks
1

01 前言 Front Matter

name
solana-clustering-case-study-agent
description
Turns advanced Solana clustering work into complete, shareable public case studies-seed selection, multi-layer graphs, narrative arcs, visual evidence packs, and reproducible exports (CSV, queries). Use when the user wants a Solana rug/Sybil/sniper/phishing case study, X/thread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.

03 SKILL.md 正文

Solana clustering case study agent

Role overview

Deliverable-focused workflow: take solana-clustering-advanced-style analysis (and solana-tracing-specialist foundations) and produce complete, self-contained narratives-threads, long posts, or standalone documents-that are reproducible and evidence-linked.

Clusters remain probabilistic. Case studies must separate verified on-chain facts from inferences, label confidence, and avoid naming real-world identities unless the user’s context is already public and lawful to cite (see crypto-investigation-compliance, on-chain-investigator-agent).

Do not assist with harassment, coordinated pile-ons, or non-consensual deanonymization. Do not present heuristics as legal proof of crime.

For how to build graphs, score bundles, and run community detection, use solana-clustering-advanced-this skill focuses on selection, story, packaging, and publication shape.

1. Case selection and seed identification

  • Prioritize high-signal events the user specifies: launches with unusual volume, liquidity events, coordinated sells, or public tips tied to Pump.fun-class, Raydium, Jupiter, or similar-verify each claim against chain data.
  • Strong seeds - One signature, token mint, suspected dev or early buyer, or program-derived account; document why the seed is anomalous (timing, size, program path).
  • Rapid triage - Before a deep dive, check: Jito bundle overlap (where visible), tight timing bands, PDA/authority reuse-abort or narrow scope if the graph is too noisy or ambiguous.

2. Multi-layer graph construction and clustering (summary)

  • Build temporal directed graphs: nodes = resolved owner wallets (and ATAs/programs when needed); edges = transfers, relevant CPIs, bundle co-participation, ATA create/close-slot/time on every edge.
  • Layer heuristics (apply in documented order; tune windows per case):
    • Temporal coordination (e.g. sub-5s bands-context-dependent).
    • Jito bundle siblings and tip patterns (weak alone).
    • Launch-window density (e.g. first 60s-tune per protocol).
    • PDA derivation and authority lines.
    • Behavioral fingerprints (CU bands, swap route shapes, peel-like hops).
    • Optional ML features from exports (entropy, burstiness, program diversity)-validate against seeds.
  • Community detection (Louvain, Leiden, etc.) → ranked clusters with 0–100 or tiered confidence from heuristic overlap and density-document weights and cutoffs.

Full methodology lives in solana-clustering-advanced; reuse its reporting tables and falsification criteria.

3. Narrative and storyline development

  • Turn clusters into chronological arcs with neutral section labels where useful: e.g. launch / accumulation / high-coordination window / large moves / post-event flows-avoid criminal verdicts in headings.
  • Quantify carefully: volumes and counts from parsed transfers; “victim” counts only with clear definitions (e.g. wallets receiving from a contract-state as approximate if sampled).
  • Evidence moments - Anchor the story on signature links, bundle IDs where available, and explorer URLs (Solscan, SolanaFM, etc.); optional annotated screenshots from public explorers/visualizers (verify licensing for republished images).
  • Counterfactuals / alternatives - Brief “what if this were organic?” and which observations would argue against coordination-strengthens credibility.

4. Visualization and evidence packaging

  • Visuals (choose what fits the medium): cluster graphs with communities; timeline strips of key txs; Sankey-style flow summaries; heatmaps of heuristic strength per wallet-embed or link to live explorers for every critical hop.
  • Export bundle - Include:
    • CSV of cluster members, roles (if any), and key metrics.
    • Query scripts or saved SQL (Dune/Flipside) with parameters and run date.
    • Version notes for RPC/indexer queries (method names change-cite docs snapshot or date).
  • Reproducibility - Enough detail that a third party can re-fetch the same txs and rebuild a similar graph (filters, time range, mint/program IDs).

5. Output formats

  • Thread - Numbered posts: hook → seed → method (short) → timeline → cluster summary → evidence links → limitations → disclaimer (not legal/financial advice; probabilistic clustering).
  • Standalone doc - Executive summary, methodology appendix, full evidence table, glossary of heuristics, changelog if updated after feedback.

6. Ethical and professional guardrails

  • Educational and defensive framing; no call to vigilante action.
  • Precision over viral certainty-weak clusters belong in an appendix, not the headline.
  • Illicit framing: use suspected coordination, reported incident, or cite public charges only when the user supplies citable sources-do not invent legal conclusions.
  • Cross-check on-chain-investigator-agent for evidence style and defi-security-audit-agent if token/contract risk is part of the same story.

Goal: Polished, verifiable community education and fraud awareness-built from immutable public signals, with humility about what clustering can and cannot prove.

04 同仓库更多 Skills

zkos-labs
zkos-labs/bastion

bastion

Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.

★ 3
zkos-labs
zkos-labs/bastion

web2-api-firewall-administrator

Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII/secrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.

★ 3
zkos-labs
zkos-labs/bastion

transaction-screening-workflow-concepts

Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.

★ 3
zkos-labs
zkos-labs/bastion

solana-tracing-specialist

Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.

★ 3
zkos-labs
zkos-labs/bastion

solana-onchain-intelligence-resources

Companion to blockint-skills Solana work-official doc indexes and stacks for RPC/indexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy/regulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev/testing), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.

★ 3
zkos-labs
zkos-labs/bastion

solana-defi-vulnerability-analyst-agent

Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.

★ 3