agentleFS
usernameisthebestofthebestusernameisthebestofthebest/claude-recap/skills/list-topics/SKILL.md

list-topics

Skill2 starsChanged 9 months agoMITView on GitHub

Use when the user asks about topics discussed in the current session, wants to see a topic list, or asks what has been talked about.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. microsoft/skills-for-copilot-studio★ 486same 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run extract-topic.js with __all__ mode:

    line 24
  2. Distinctive:

    If JSONL file doesn't exist or no topics found after filtering, tell the user no topics exist yet.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

list-topics

Overview

Lists all topic slugs found in the current session's JSONL history.

Instructions

  1. Get the session ID from the SessionStart injection in your context: [SessionStart] session=SESSION_ID source=...
  2. Get the plugin scripts path from the SessionStart injection: Plugin scripts path: /path/to/scripts
  3. Get the project ID from the SessionStart injection: Your persistent memory is stored at: $HOME/.memory/projects/PROJECT_ID/ Extract the PROJECT_ID segment (e.g. -Users-alex-my-app).
  4. Run extract-topic.js with __all__ mode:
node "<plugin_scripts_path>/extract-topic.js" "$HOME/.claude/projects/<project_id>/<session_id>.jsonl" __all__
  1. Filter out __untagged__ from the output, then present using this exact format:
Session Topics:
1. **topic-slug-a**
2. **topic-slug-b**
3. **topic-slug-c**

Current: **topic-slug-c**

Rules

  • If JSONL file doesn't exist or no topics found after filtering, tell the user no topics exist yet.
  • Current topic is from your topic tag (the › \slug`` you've been outputting).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.