[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72131HP2PBV8CWYGSWV73Y6":3,"skill-same:01M72131HP2PBV8CWYGSWV73Y6":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72131HP2PBV8CWYGSWV73Y6","solana-clustering-case-study-agent",null,"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\u002FSybil\u002Fsniper\u002Fphishing case study, X\u002Fthread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.","zkos-labs\u002Fbastion","zkos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263369112?v=4","01M720WZH0GD7FAKBP5PSGF4TG","ZKOS Labs","01M720WZHP9JV5NZVQCHA6XJ3M",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-clustering-case-study-agent\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: solana-clustering-case-study-agent\ndescription: 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\u002FSybil\u002Fsniper\u002Fphishing case study, X\u002Fthread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.\n---\n\n# Solana clustering case study agent\n\n## Role overview\n\n**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**.\n\n**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**).\n\nDo **not** assist with harassment, coordinated pile-ons, or non-consensual deanonymization. Do **not** present heuristics as **legal proof** of crime.\n\nFor **how** to build graphs, score bundles, and run community detection, use **solana-clustering-advanced**-this skill focuses on **selection, story, packaging, and publication shape**.\n\n## 1. Case selection and seed identification\n\n- **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.\n- **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).\n- **Rapid triage** - Before a deep dive, check: Jito bundle overlap (where visible), tight timing bands, PDA\u002Fauthority reuse-**abort** or narrow scope if the graph is too noisy or ambiguous.\n\n## 2. Multi-layer graph construction and clustering (summary)\n\n- Build **temporal directed graphs**: nodes = resolved **owner** wallets (and ATAs\u002Fprograms when needed); edges = transfers, relevant CPIs, bundle co-participation, ATA create\u002Fclose-**slot\u002Ftime** on every edge.\n- **Layer heuristics** (apply in documented order; tune windows per case):\n  - Temporal coordination (e.g. sub-5s bands-**context-dependent**).\n  - Jito bundle siblings and tip **patterns** (weak alone).\n  - Launch-window density (e.g. first **60s**-tune per protocol).\n  - PDA derivation and **authority** lines.\n  - Behavioral fingerprints (CU bands, swap route shapes, peel-like hops).\n  - Optional **ML** features from exports (entropy, burstiness, program diversity)-**validate** against seeds.\n- **Community detection** (Louvain, Leiden, etc.) → ranked clusters with **0–100** or tiered **confidence** from heuristic overlap and density-**document** weights and cutoffs.\n\n**Full methodology** lives in **solana-clustering-advanced**; reuse its reporting tables and falsification criteria.\n\n## 3. Narrative and storyline development\n\n- Turn clusters into **chronological** arcs with neutral section labels where useful: e.g. launch \u002F accumulation \u002F high-coordination window \u002F large moves \u002F post-event flows-**avoid** criminal verdicts in headings.\n- **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).\n- **Evidence moments** - Anchor the story on **signature links**, bundle IDs where available, and **explorer** URLs (Solscan, SolanaFM, etc.); optional **annotated** screenshots from public explorers\u002Fvisualizers (**verify** licensing for republished images).\n- **Counterfactuals \u002F alternatives** - Brief “what if this were organic?” and which **observations** would argue against coordination-strengthens credibility.\n\n## 4. Visualization and evidence packaging\n\n- **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.\n- **Export bundle** - Include:\n  - **CSV** of cluster members, roles (if any), and key metrics.\n  - **Query scripts** or saved SQL (Dune\u002FFlipside) with **parameters** and **run date**.\n  - **Version** notes for RPC\u002Findexer queries (method names change-cite docs snapshot or date).\n- **Reproducibility** - Enough detail that a third party can **re-fetch** the same txs and **rebuild** a similar graph (filters, time range, mint\u002Fprogram IDs).\n\n## 5. Output formats\n\n- **Thread** - Numbered posts: hook → seed → method (short) → timeline → cluster summary → evidence links → limitations → **disclaimer** (not legal\u002Ffinancial advice; probabilistic clustering).\n- **Standalone doc** - Executive summary, methodology appendix, full evidence table, glossary of heuristics, changelog if updated after feedback.\n\n## 6. Ethical and professional guardrails\n\n- **Educational** and **defensive** framing; no call to vigilante action.\n- **Precision** over viral certainty-weak clusters belong in an appendix, not the headline.\n- **Illicit** framing: use **suspected coordination**, **reported incident**, or cite **public** charges only when the user supplies **citable** sources-do **not** invent legal conclusions.\n- Cross-check **on-chain-investigator-agent** for evidence style and **defi-security-audit-agent** if token\u002Fcontract risk is part of the same story.\n\n**Goal:** Polished, **verifiable** community education and fraud awareness-built from **immutable** public signals, with humility about what clustering can and cannot prove.\n","# Solana clustering case study agent\n\n## Role overview\n\n**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**.\n\n**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**).\n\nDo **not** assist with harassment, coordinated pile-ons, or non-consensual deanonymization. Do **not** present heuristics as **legal proof** of crime.\n\nFor **how** to build graphs, score bundles, and run community detection, use **solana-clustering-advanced**-this skill focuses on **selection, story, packaging, and publication shape**.\n\n## 1. Case selection and seed identification\n\n- **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.\n- **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).\n- **Rapid triage** - Before a deep dive, check: Jito bundle overlap (where visible), tight timing bands, PDA\u002Fauthority reuse-**abort** or narrow scope if the graph is too noisy or ambiguous.\n\n## 2. Multi-layer graph construction and clustering (summary)\n\n- Build **temporal directed graphs**: nodes = resolved **owner** wallets (and ATAs\u002Fprograms when needed); edges = transfers, relevant CPIs, bundle co-participation, ATA create\u002Fclose-**slot\u002Ftime** on every edge.\n- **Layer heuristics** (apply in documented order; tune windows per case):\n  - Temporal coordination (e.g. sub-5s bands-**context-dependent**).\n  - Jito bundle siblings and tip **patterns** (weak alone).\n  - Launch-window density (e.g. first **60s**-tune per protocol).\n  - PDA derivation and **authority** lines.\n  - Behavioral fingerprints (CU bands, swap route shapes, peel-like hops).\n  - Optional **ML** features from exports (entropy, burstiness, program diversity)-**validate** against seeds.\n- **Community detection** (Louvain, Leiden, etc.) → ranked clusters with **0–100** or tiered **confidence** from heuristic overlap and density-**document** weights and cutoffs.\n\n**Full methodology** lives in **solana-clustering-advanced**; reuse its reporting tables and falsification criteria.\n\n## 3. Narrative and storyline development\n\n- Turn clusters into **chronological** arcs with neutral section labels where useful: e.g. launch \u002F accumulation \u002F high-coordination window \u002F large moves \u002F post-event flows-**avoid** criminal verdicts in headings.\n- **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).\n- **Evidence moments** - Anchor the story on **signature links**, bundle IDs where available, and **explorer** URLs (Solscan, SolanaFM, etc.); optional **annotated** screenshots from public explorers\u002Fvisualizers (**verify** licensing for republished images).\n- **Counterfactuals \u002F alternatives** - Brief “what if this were organic?” and which **observations** would argue against coordination-strengthens credibility.\n\n## 4. Visualization and evidence packaging\n\n- **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.\n- **Export bundle** - Include:\n  - **CSV** of cluster members, roles (if any), and key metrics.\n  - **Query scripts** or saved SQL (Dune\u002FFlipside) with **parameters** and **run date**.\n  - **Version** notes for RPC\u002Findexer queries (method names change-cite docs snapshot or date).\n- **Reproducibility** - Enough detail that a third party can **re-fetch** the same txs and **rebuild** a similar graph (filters, time range, mint\u002Fprogram IDs).\n\n## 5. Output formats\n\n- **Thread** - Numbered posts: hook → seed → method (short) → timeline → cluster summary → evidence links → limitations → **disclaimer** (not legal\u002Ffinancial advice; probabilistic clustering).\n- **Standalone doc** - Executive summary, methodology appendix, full evidence table, glossary of heuristics, changelog if updated after feedback.\n\n## 6. Ethical and professional guardrails\n\n- **Educational** and **defensive** framing; no call to vigilante action.\n- **Precision** over viral certainty-weak clusters belong in an appendix, not the headline.\n- **Illicit** framing: use **suspected coordination**, **reported incident**, or cite **public** charges only when the user supplies **citable** sources-do **not** invent legal conclusions.\n- Cross-check **on-chain-investigator-agent** for evidence style and **defi-security-audit-agent** if token\u002Fcontract risk is part of the same story.\n\n**Goal:** Polished, **verifiable** community education and fraud awareness-built from **immutable** public signals, with humility about what clustering can and cannot prove.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fsolana-clustering-case-study-agent",1,"https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion","https:\u002F\u002Fbastionagentique.com\u002F","https:\u002F\u002Fgithub.com\u002Fzkos-labs","https:\u002F\u002Fzkoslabs.org","A research-driven builders' organization advancing programmable trust infrastructure for Ethereum and interoperable open networks.","2026-11-13 21:01:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zkos-labs\u002Fbastion --skill solana-clustering-case-study-agent",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill solana-clustering-case-study-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill solana-clustering-case-study-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-clustering-case-study-agent\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7213RCWV886P2R63MTQAEGW","bastion","Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7213MYSJE23KMMTD95Y3M3Z","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\u002Fsecrets 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.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb2-api-firewall-administrator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7213HE08PE43M2H0QZENZP2","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.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7213DQ7TVE986643SR105Y4","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\u002FJito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-tracing-specialist\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M72138PB2HTKJ0J39WNSRCRR","solana-onchain-intelligence-resources","Companion to blockint-skills Solana work-official doc indexes and stacks for RPC\u002Findexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy\u002Fregulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev\u002Ftesting), 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.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-onchain-intelligence-resources\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent","Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative 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\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[]]