tag-organize

tag-organize is a skill for Claude Code from wpsnote/wpsnote-skills. It costs 122 tokens per session (3,527 once invoked), scanned A, original, MIT.

A workflow for organizing file-level tags in WPS Notes, a cloud note-taking service. It uses note statistics, tag searches, note details, note searches, and tag-management tools.

In plain words
What is it for?
Use it to add, clean up, reorganize, or redesign the tag system for a collection of WPS Notes.
Why use it?
It addresses messy, excessive, or inconsistent tags without changing the note content itself.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Part of the base-skills plugin — 6 skills shipped together

Good fit Use it to add, clean up, reorganize, or redesign the tag system for a collection of WPS Notes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wpsnote/wpsnote-skills/tag-organize
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wpsnote/wpsnote-skills --skill tag-organize
Clone the repo
git clone --depth 1 https://github.com/wpsnote/wpsnote-skills

Made for: Claude Code.

Or install base-skills, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tag-organize

README.md
[![agentmods](https://agentmods.dev/badge/skills/wpsnote/wpsnote-skills/tag-organize/github.svg)](https://agentmods.dev/skills/wpsnote/wpsnote-skills/tag-organize)
Your own site
<a href="https://agentmods.dev/skills/wpsnote/wpsnote-skills/tag-organize"><img src="https://agentmods.dev/badge/skills/wpsnote/wpsnote-skills/tag-organize/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tag-organize

Your own site · 80×15
<a href="https://agentmods.dev/skills/wpsnote/wpsnote-skills/tag-organize"><img src="https://agentmods.dev/badge/skills/wpsnote/wpsnote-skills/tag-organize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,527 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00122 $0.03527
Opus 5.5 $0.00049 $0.01411
Sonnet 5.5 $0.00024 $0.00705
Haiku 4.5 $0.00012 $0.00353

Measured 1mo ago against content hash 6c17d10fd9d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tag-organize scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/tag-organize/SKILL.md · 269 lines

How it starts

The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.

笔记标签整理核心原则与流程

核心原则

整理标签不是在执行一套标准方法论,而是在服务一个具体的人。没有统一的「正确」分类方式,一切决策以用户的实际需求为准。

整理的价值只来自三个方向,不能带来其中任何一项的改动都不值得做:

  • 提升使用效率:减少维护负担,降低分类焦虑
  • 提升检索效率:让用户更快找到目标内容
  • 带来新的知识连接视角:发现原来看不到的关联

不要在任务开始时反问用户「你想整理什么范围、怎么整理」。用户找 AI 来整理,本身就意味着他不想自己做这些判断。AI 的职责是主动给出具体方案,让用户做选择题,而不是问答题。


操作安全约束

当前阶段只做打标。 笔记标签是文件级独立对象,通过 wps-note 专用工具 manage_note_tags 增删改;不要再通过 edit_block、batch_edit 或 <tag> XML 修改标签。

硬性规则,每次操作都必须遵守:

  1. 修改标签只用 manage_note_tags:

    • 查询某笔记当前标签:manage_note_tags({ note_id })(只传 note_id 即为查询)
    • 添加:manage_note_tags({ note_id, add: ["工作/项目"] })
    • 删除:manage_note_tags({ note_id, remove: ["旧标签"] })
    • 重命名 / 合并:在同一次调用中组合 remove + add
    • 传给工具的标签名不带 # 前缀;#工作/项目 只用于对用户展示时的习惯写法
  2. 跨笔记的全局操作必须先 ask_user 确认:标签的全局重命名、合并、批量删除(影响 2 篇以上笔记)属于跨笔记批量操作,执行前必须调用 ask_user。

  3. 意图不明的笔记直接跳过:无法确定内容主题或用途时,不猜测、不修改,在方案中列为「未处理」告知用户。

  4. 不删除任何笔记:无论笔记看起来多空,都不在此阶段做任何笔记删除。

  5. 确认必须用 ask_user 工具:禁止用文本提问代替 ask_user 调用——文本提问不会暂停执行,用户无法介入。调用 ask_user 的同一轮中禁止执行写入工具。


WPS 笔记系统行为说明

在 WPS 笔记中操作时,以下系统行为会影响结果,必须了解:

行为 说明 应对方式
/ 表示层级分隔 标签名中的 / 是层级分隔符,WPS 自动将其解析为父子关系 写完整路径调用 manage_note_tags({ note_id, add: ["工作/项目"] })
区分大小写 标签按用户输入原样存储,TODO、Todo、todo 是三个不同的标签 比对标签时按字面比对,不做大小写归一
标签输入限制 最多 10 级层级,每级最多 20 字符;禁用 \ : * ? " < > | 与 emoji;同一文档内不允许重复标签 生成新标签时主动遵守这些限制;命中系统报错时根据返回信息调整后重试

任务流程

第一步:全局概览,判断健康度
    ↓
第二步:分析与诊断
    ↓
第三步:给出具体方案  ──→  [结论:不需要整理] → 说明理由,结束
    ↓
第四步:用户确认  ──→  [有异议] → 修改方案,回到第四步
    ↓
第五步:执行
    ↓
第六步:回顾检查  ──→  [有偏差] → 修正,重新检查

第一步:全局概览,判断健康度

选择合适的工具查看当前笔记文件和标签列表,了解当前笔记系统的整体状况,再决定深入哪些地方。

第一层:必做(全局概览)
  1. get_note_stats({ detailed: true }) — 一次调用获得:

    • 文件总数、标签总数、无标签文件数
    • 每个标签下的文件数量分布(按笔记数降序,最多返回 30 个;标签较多时结合 find_tags() 看全量)
    • 近期更新的文件列表
  2. find_tags() — 获得:

    • 完整的标签层级结构(父子关系、命名)
    • 识别命名风格、层级逻辑、可疑标签名

完成这两步后,通常已能发现大多数问题(颗粒度失衡、命名不一致、无标签文件过多等),并形成整理方向的初步判断。

Read the full file on GitHub · 269 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 269 lines · 122 tokens per session scan A 6c17d10fd9d1

Subscribe to this mod's changes

tag-organize is a skill published in the GitHub repository wpsnote/wpsnote-skills (183 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 3,527 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

dsh-onboarding

Guidance for helping someone use DeepSeek Harness, a local runtime for coding agents, for the first time. It explains the runtime, profiles, workspace, permissions, and how extensions are discovered.

pingfanfan/hello-dsh · 60 tokens

query

Answer questions about the wiki by searching, reading, and synthesizing relevant scraps with [[Title]] citations. Use this when the user wants to query the wiki, ask what they have written about a topic, compare scraps, find related notes, or pull a synthesized overview from existing scraps.

boykush/scraps · 61 tokens

scratch

Organize knowledge from an agent session into a scratchpad — a folder of files plus a scratchpad.json manifest. Use when a task generates notes, snippets, command output, diagrams, or artifacts worth keeping together for a session/activity.

NikiforovAll/scratchpad · 49 tokens

clip

Pin an answer from this conversation to Mycelium, verbatim. Use only when the user explicitly invokes $clip or asks to clip or pin an answer to Mycelium.

krapie/mycelium · 38 tokens

redfox-subscribe

A central menu for managing subscriptions to scheduled content updates, such as account tracking, AI digests, industry reports, and trending-topic reports. It routes each request to the specific source that performs the subscription.

redfox-data/redfox-community-dsh · 140 tokens

anywrite

Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.

sendralt/agentic-awesome-skills · 37 tokens