listen
Skill1 starsChanged 3 months agoMITView on GitHub
Mine opencode session transcripts for post-worthy ideas and turn them into X posts. Use when the user says "listen", "/listen", "mine my sessions for post ideas", "content ideas from my work", "brainstorm posts", "what should I post", or wants short-form post drafts from dev sessions. Two modes: extraction (default) and brainstorm.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- allthriveai/amplifytheir own version, first seen Aug 30, 2026
- PatrickJaiin/claude-code-connecttheir own version, first seen Jul 21, 2026
- adarsh-goswamii/skillstheir own version, first seen May 10, 2026
- terminator1333/claude-listentheir own version, first seen Apr 23, 2026
- shreyaskarnik/voice-mcptheir own version, first seen Feb 10, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- shreyaskarnik/voice-mcp★ 17same name
- PatrickJaiin/claude-code-connect★ 2same name
- adarsh-goswamii/skills★ 1same name
- terminator1333/claude-listen★ 1same name
- allthriveai/amplify★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- ai-sdkSkill
- anti-slopSkill
- architecture-auditSkill
- browseSkill
- cavemanSkill
- context-budgetSkill
- design-mdSkill
- e2e-testingSkill
- error-handlingSkill
- find-skillsSkill
- fresh-context-reviewSkill
- frontend-designSkill
- graph-memorySkill
- grill-meSkill
- manual-qa-planSkill
- next-best-practicesSkill
- nextjs-app-router-patternsSkill
- prd-to-issuesSkill
- project-feedbackSkill
- project-memorialSkill
- scrollcraftSkill
- sequential-afk-runnerSkill
- shadcnSkill
- tddSkill
- vercel-react-best-practicesSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Read the summary. If sessions_dumped: 0 → say "nothing new since <date>", stop.
- Very specific: line 27
Read dump.md (in chunks if large).
- Very specific: line 35
Write each idea to ideas/YYYY-MM-DD-<slug>.md (template below).
- Very specific: line 36
Only after idea files are written, update state (use max_time_updated_ms and session_ids from the script summary):
- Very specific: line 44
If state.json is missing, create {"last_scan_ms": 0, "scanned_sessions": []} first.
- Distinctive: line 57
all lowercase, short sentences, no emojis, no hashtags
- Distinctive: line 88
No auto-posting anywhere, ever.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Listen
Turns work sessions into content. Data dir: ~/.config/opencode/listen/
(state.json, ideas/*.md, transient dump.md). Source:
~/.local/share/opencode/opencode.db (opencode only, always read-only).
Mode 1: extract (default)
- Run:
Flags:~/.config/opencode/skills/listen/scripts/extract.sh--since <ms>(override state),--all(ignore state),--limit N(max 15). First-ever run defaults to a 3-day lookback. - Read the summary. If
sessions_dumped: 0→ say "nothing new since<date>", stop. Never touch the backlog. - Read
dump.md(in chunks if large). - Extract AT MOST 5 ideas per run, matching the gold criteria:
- lesson — clever fixes, gotchas, tooling opinions, hard-won lessons
- take — opinions, contrarian takes, tooling/AI philosophy
- story — surprising, funny, or story-like moments
- Dedup FIRST:
ls ~/.config/opencode/listen/ideas/, read near-matching files. Same insight → append**resurfaced:** YYYY-MM-DDto the existing file; never fork a duplicate. - Write each idea to
ideas/YYYY-MM-DD-<slug>.md(template below). - Only after idea files are written, update state (use
max_time_updated_msandsession_idsfrom the script summary):
If state.json is missing, createcd ~/.config/opencode/listen && jq --argjson ms <MAX_MS> \ --argjson ids '["ses_a","ses_b"]' \ '.last_scan_ms = $ms | .scanned_sessions += $ids' \ state.json > state.tmp && mv state.tmp state.json{"last_scan_ms": 0, "scanned_sessions": []}first. - Report: N sessions scanned, M ideas written, K dupes linked — then one line per new idea: title (type) + hook.
Mode 2: brainstorm (/listen brainstorm)
- List backlog: idea files with
status: idea, grouped by type. - Empty backlog → offer to run extraction first.
- Walk ONE idea at a time: show title, insight, hook. User picks:
draft now / must-write / skip / archive.
- must-write → draft immediately, no further questions.
- Voice — terse lowercase:
- all lowercase, short sentences, no emojis, no hashtags
- line 1 = hook, then payoff, optional 1 line of context
- threads: numbered posts, each ≤280 chars, each stands alone
- one idea per post; concrete beats abstract
- Accepted draft → append a
## draftsection to the idea file and setstatus: drafted. - Dead idea →
status: archived. Never delete files. - Close with counts: drafted / archived / still ideas.
Idea file template
---
status: idea
type: lesson
date: YYYY-MM-DD
source_session: ses_...
title: short title
---
the insight, paraphrased, 1-3 sentences.
**why post-worthy:** ...
**hook:** rough first lineSecurity (hard rules)
- Idea files NEVER contain: secrets, API keys, tokens, real usernames/emails, wallet addresses, private paths, or code quoted verbatim. Paraphrase.
- The DB is opened read-only (
mode=ro). Never write to it. dump.mdstays local; never paste large raw chunks into chat.- No auto-posting anywhere, ever.
Edge cases
- state.json missing → extractor defaults to 3-day lookback (not
--all) - dump hit byte cap → summary reports skipped sessions; they return next run
- DB locked/missing → script exits cleanly with an error; tell the user to retry
- session with no text parts → skipped silently by the script
- duplicate insight on rescan →
resurfacedline, no fork
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

