USDC Base Activity Report – Business Analysis Skill

This skill guides an AI agent through a complete, repeatable analysis of the market opportunity for a USDC transaction monitoring and reporting service on Base. Follow the steps below to produce the required sections of the report.

1. Gather Input Data

Ask the user for any of the following (optional):

• Base wallet address or contract address
• Specific USDC token ticker (USDC)
• Target customer segment (e.g., small business, DAO, trader)
• Desired revenue goal or price expectation
• Sample transaction list (CSV, JSON, or plain text)

If the user provides incomplete data, assume a generic USDC wallet with moderate activity (≈ 500‑1,000 daily transactions) and a broad target market (crypto‑savvy SMEs and DAOs).

2. Structure the Report

Create a markdown document with the exact headings listed in the original request. Populate each section using the data collected or the default assumptions.

2.1 Executive Summary

• Briefly describe the opportunity.
• Identify who would pay (e.g., DAOs needing payout summaries, SMEs needing payment reconciliation).
• State a high‑level recommendation (e.g., “Build prototype”).

2.2 Transaction Use Case

• Explain the type of USDC activity (payments, transfers, protocol fees).
• Highlight why this activity matters (settlement, accounting, compliance).
• Identify the pain point (manual reconciliation, lack of plain‑English summaries).

2.3 Target Customer

List relevant segments and a one‑sentence rationale for each.

2.4 Proposed Paid Agent Skill

• Skill name: e.g., base-usdc-report
• Function: Generate a plain‑English report of recent USDC activity for a given address or contract.
• Required inputs: wallet/contract address, date range, optional filters (inflow/outflow, token amount).
• Output: Summary paragraph + bullet list of key metrics + optional CSV attachment.
• Value proposition: Saves time, reduces accounting errors, provides quick insight for non‑technical stakeholders.

2.5 Monetization Model

• Suggest a per‑invocation price (e.g., 0.02 USDC).
• Estimate usage frequency (daily for active wallets, weekly for occasional users).
• Provide revenue scenarios for 10, 100, 1,000 users.

2.6 Example User Requests

Create three realistic prompts, such as:

1. “Give me a weekly USDC payment summary for wallet 0xABC…”
2. “Show the top 5 inflows to my DAO treasury on Base last month.”
3. “Generate a CSV of all USDC transfers over $10,000 for address 0xDEF…”.

2.7 Feasibility Score

Score 1‑100 based on:

• Data availability (BaseScan API, public RPC)
• Repeatability (same query pattern each run)
• Buyer urgency (accounting deadlines, treasury monitoring)
• Automation ease (simple RPC calls, CSV parsing)
• Competitive advantage (plain‑English focus)

2.8 Risks and Limitations

Enumerate at least five risks:

• Missing or delayed on‑chain data
• Incorrect wallet labeling (e.g., exchange hot wallets)
• Potential regulatory concerns around financial advice
• Tax‑reporting accuracy limits
• Market demand uncertainty for low‑volume users

2.9 Final Recommendation

Choose one of:

• Build immediately
• Build prototype
• Watch for demand
• Do not build

Provide a concise justification.

3. Execution Flow (Pseudo‑code)

1. Receive user input.
2. If any required field missing → ask follow‑up questions.
3. Query Base RPC / BaseScan for USDC transfer events:
   - filter by address, token contract (0xa0b86991...), date range.
4. Aggregate:
   - total inflow, total outflow, net balance change.
   - top counterparties, largest transfers.
5. Format results:
   - Plain‑English paragraph.
   - Bullet list of key metrics.
   - Optional CSV string.
6. Assemble markdown report using sections 1‑9.
7. Return the markdown to the user.

4. Tips for High‑Quality Output

• Be concise in the executive summary (2‑3 sentences).
• Use plain language; avoid technical jargon unless in a separate “Technical Details” note.
• When estimating revenue, be realistic: assume 20‑30 % conversion from free users to paying users.
• Highlight time‑saving as the primary value driver.
• Cite public data sources (BaseScan, RPC) to reassure users about data reliability.

---

Result: By following this guide, the AI agent will produce a comprehensive, business‑focused analysis that helps stakeholders decide whether to invest in a USDC Base activity reporting skill.