amp-api-awareness
Extract hidden Amp API patterns from local thread data via DuckDB analysis
npx skills add majiayu000/claude-skill-registry --skill amp-api-awareness --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Amp API Awareness Discover Amp's undocumented API by mining local thread storage. ## Data Sources | Source | Path | Format | |--------|------|--------| | Threads | `~/.local/share/amp/threads/*.json` | JSON per thread | | History | `~/.claude/history.jsonl` | JSONL sessions | | Projects | `~/.claude/projects/*/*.jsonl` | JSONL per project | ## Quick Extraction ### Count all threads ```bash ls ~/.local/share/amp/threads/*.json | wc -l ``` ### Sample thread structure ```bash cat ~/.local/share/amp/threads/T-*.json | head -1 | jq 'keys' # Expected: ["id", "title", "created", "updatedAt", "messages", ...] ``` ### DuckDB unified query ```sql -- Load all threads CREATE TABLE amp_threads AS SELECT * FROM read_json('~/.local/share/amp/threads/*.json', columns={id: 'VARCHAR', title: 'VARCHAR', created: 'BIGINT', messages: 'JSON[]', creatorUserID: 'VARCHAR'}, ignore_errors=true); -- Extract message patterns SELECT id, title, len(messages) as msg_count, abs(hash(id)) % 3 - 1 as trit FROM amp_threads ORDER BY created DESC LIMIT 20; ``` ## API Discovery Patterns ### 1. Tool Usage Extraction ```sql -- Find all tool invocations across threads SELECT json_extract_string(msg, '$.type') as msg_typ
- Data Sources
- Quick Extraction
- Count all threads
- Sample thread structure
- DuckDB unified query
- API Discovery Patterns
- 1. Tool Usage Extraction
- 2. MCP Server Detection
- 3. Thread Schema Discovery
- Full Statistics (2,424 threads, 118,951 messages)
- Core Tools
- MCP Servers
- Agent Modes
- Known Endpoints & APIs
ls ~/.local/share/amp/threads/*.json | wc -l
cat ~/.local/share/amp/threads/T-*.json | head -1 | jq 'keys'
Via find_thread DSL (repo: filter scopes to workspace)
find_thread "repo:i after:30d"
Export to DuckDB
duckdb amp-threads.duckdb -c "
CREATE TABLE threads AS
SELECT * FROM read_json('~/.local/share/amp/threads/*.json',
Query patterns
SELECT title, created FROM threadsWhat does the amp-api-awareness skill do?
Extract hidden Amp API patterns from local thread data via DuckDB analysis
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill amp-api-awareness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.