usernameisthebestofthebestusernameisthebestofthebest/claude-recap/skills/ignore-topic/SKILL.md

ignore-topic

Skill2 starsChanged 9 months agoMITView on GitHub

Use when the user wants to ignore, skip, or exclude specific topics from being archived. Triggers on "ignore topic", "don't archive", "skip topic", "stop remembering", "list ignored topics", "remove ignore rule".

In this repository3 other files it gives its agents.
- list-topicsSkill
- rememberSkill
- save-topicSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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

Very specific:
If no patterns provided, ask for patterns (space-separated, glob supported: *, ?, [...]).
line 27
Distinctive:
Ask scope via AskUserQuestion:
line 28
Distinctive:
If no pattern provided, ask which pattern to remove.
line 42
Distinctive:
Ask scope (global or project).
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

ignore-topic

Manage .ignore rules — glob patterns that prevent matching topic slugs from being archived. Topics still get tagged but archival is skipped (no LLM summary call, no file written).

Step 1: Determine operation

Parse the user's message for operation (add/remove/list) and patterns. If clear, skip to Step 2.

Otherwise, ask using AskUserQuestion:

What would you like to do?
- Add: Add ignore patterns (topics matching these will not be archived)
- Remove: Remove an existing ignore pattern
- List: Show all current ignore rules

Step 2: Execute

add:

If no patterns provided, ask for patterns (space-separated, glob supported: *, ?, [...]).

Ask scope via AskUserQuestion:

Which scope?
- Global: applies to all projects (~/.memory/.ignore)
- Project: applies only to this project

Run:

bash "<plugin_scripts_path>/ignore-topic.sh" add "<scope>" <pattern1> [pattern2 ...]

<scope>: global or the project dir path from SessionStart context.

remove:

If no pattern provided, ask which pattern to remove.
Ask scope (global or project).

Run:

bash "<plugin_scripts_path>/ignore-topic.sh" remove "<scope>" "<pattern>"

list:

bash "<plugin_scripts_path>/ignore-topic.sh" list "<project_dir>"

Path resolution

<plugin_scripts_path>: from SessionStart injection Plugin scripts path: ...
<project_dir>: from SessionStart injection Your persistent memory is stored at <project_dir>

Examples

User says	Operation	Scope question?
`/ignore-topic add git-* lint-fix`	add `git-*` and `lint-fix`	Yes
`/ignore-topic`	Ask all	Yes
`/ignore-topic list`	list	No
"don't archive run-tests topics"	add `run-tests`	Yes
`/ignore-topic remove git-*`	remove `git-*`	Yes

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.

Check your setup, free