Skip to content

aboylabs/ai-agent-skills / skills/research/crypto-token-analysis

crypto-token-analysis

Verified

Deep-dive framework for analyzing crypto tokens β€” market data, liquidity health, tokenomics, unlock schedules, and risk assessment. Combines on-chain data, API queries, and multi-source validation to generate actionable investment verdicts.

references/indonesian-analysis-template.md

View on GitHub
# Indonesian Analysis Template

When user writes in Bahasa Indonesia, use this comprehensive 11-section template for crypto/DePIN project analysis.

## Template Structure

```markdown
# πŸ” ANALISA MENDALAM: [PROJECT NAME]

**Tweet/Announcement:** "[Quote exact text]"
**Tanggal:** [Date]
**Engagement:** [likes] likes, [RT] RT, [replies] replies

---

## 🧠 1. CONTEXT EXTRACTION

**Isi Tweet/Announcement:**
- [Specific content]
- Ini: [product launch / partnership / campaign / teaser]

**Jenis:**
- [Classification]

**Keyword:**
- βœ…/❌ [reward / points / early users / incentivized]

---

## πŸ“Š 2. PROJECT UNDERSTANDING

**Apa itu [Project]?**
- [1-2 sentence description]

**Role di [Ecosystem]:**
- [L1 / L2 / Infra / DePIN / etc.]

**Use Case:**
- [Primary use cases]

**Unique Edge vs Kompetitor:**
- [Comparison table or bullet points]

---

## πŸ’° 3. ECOSYSTEM & BACKING

**Token: $[SYMBOL]**
- Price: $X
- Market Cap: $X (rank #X)
- Volume 24h: $X (X% of MCap)
- Circulating: X (X%)
- Total Supply: X
- ATH: $X ([date]) β€” down -X%

**Funding:**
- [VC info or "Tidak ada info public"]

**Partner Utama:**
- [List or "Tidak ada list spesifik"]

**Narrative:**
- [DePIN / AI / RWA / etc.]

---

## βš™οΈ 4. PRODUCT REALITY CHECK

**Sudah Ada:**
- βœ…/❌ Mainnet
- βœ…/❌ Testnet
- βœ…/❌ SDK/Docs
- βœ…/❌ GitHub (X stars)

**Bisa Digunakan Sekarang:**
- [Ya/Tidak + details]

**User Bisa:**
- [List of actions]

**Barrier Entry:**
- [LOW / MEDIUM / HIGH] β€” [reasoning]

---

## 🎯 5. AIRDROP / REWARD SIGNAL

**Score: X/10**

**Indikator Positif:**
- βœ… [Signal 1]
- βœ… [Signal 2]

**Indikator Negatif:**
- ❌ [Red flag 1]
- ❌ [Red flag 2]

**Pattern Comparison:**
- [Compare to successful projects]

**Airdrop Probability: X%**

**Reasoning:**
- [2-3 sentences]

---

## πŸ”— 6. USER ACTION ANALYSIS

**Apa yang bisa dilakukan sekarang:**
1. [Action 1]
2. [Action 2]

**Apakah perlu:**
- Hardware: [Ya/Tidak]
- Staking: [Ya/Tidak]
- Node: [Ya/Tidak]

**Barrier Entry:**
- [Assessment]

---

## πŸ“ˆ 7. MOMENTUM ANALYSIS

**Engagement Tweet:**
- [X] likes / [Y] followers = X% (RENDAH/NORMAL/TINGGI)

**Growth Akun:**
- [Analysis]

**Narrative Strength:**
- [Hot/Warm/Cold + reasoning]

**Verdict Momentum:** X/10

---

## ⚠️ 8. RED FLAG

1. **[Flag 1]** β€” [explanation]
2. **[Flag 2]** β€” [explanation]
3. **[Flag 3]** β€” [explanation]

**Severity:** [LOW / MEDIUM / HIGH]

---

## πŸ’‘ 9. HIDDEN ALPHA

**Insight tidak obvious:**

1. **Positioning masa depan:**
   - [Strategic insight]

2. **[Unique angle]:**
   - [Non-obvious opportunity]

3. **Comparison dengan project sukses:**
   - [Benchmark comparison]

**Verdict Alpha:** X/10

---

## πŸ’° 10. FINAL VERDICT

**Score Total: X/10**

**Airdrop/Reward Probability: X%**

**Stage: [Pre-Early / Early / Mid / Late]**

**Verdict: [FARM / RUN NODE / WATCH / SKIP]**

**Reasoning:**
- [Bullet points with βœ…/❌]

---

## 🧠 11. STRATEGI

### **[VERDICT] β†’ [Action Type]:**

**[If FARM/RUN NODE]:**

**Step-by-step:**
1. [Exact action with command]
2. [Next step]
3. [Monitoring]

**Budget:**
- Waktu: X jam/bulan
- Cost: $X-Y
- Risk: [LOW / MEDIUM / HIGH]

**Expected ROI:**
- Jika ada airdrop: $X-Y
- Jika tidak ada: -$X
- Risk/Reward: X:1

**[If WATCH]:**

**Trigger kapan masuk:**
1. **Trigger 1:** [Condition]
2. **Trigger 2:** [Condition]
3. **Trigger 3:** [Condition]

**[If SKIP]:**

**Alasan jelas:**
- [Reasoning with data]

---

## πŸ“Œ KESIMPULAN

[2-3 paragraph summary with key takeaways]

**TLDR:** [1 sentence verdict]
```

## Style Guidelines

**Tone:**
- Ringkas (concise)
- Tajam (sharp, direct)
- Fokus alpha (actionable insights)
- Tidak bertele-tele (no fluff)

**Data presentation:**
- Always include numbers (price, MCap, volume, engagement)
- Use βœ…/❌ for binary indicators
- Use tables for comparisons
- Use bold for critical findings

**Verdict format:**
- Must be tegas (decisive)
- Include probability percentage
- Provide clear action steps or entry conditions
- No hedging unless genuinely uncertain

**Language:**
- Use Bahasa Indonesia throughout
- Technical terms can stay in English (e.g., "DePIN", "TVL", "MCR")
- Numbers use period for thousands (e.g., "1.000" not "1,000")
- Currency always in USD with $ symbol
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall