ryzencool/dinox-cli-skills

dino-manage-tags

List or create Dinox tags. Use when the user wants to see their tags, add new tags, or organize their tag hierarchy.

First seen Jun 5, 2026

Installation

$ npx skills add ryzencool/dinox-cli-skills --skill dino-manage-tags

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ryzencool/dinox-cli-skills · top by installs.

npx skills add ryzencool/dinox-cli-skills

Browse all from ryzencool/dinox-cli-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch master
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.1.1
Allowed toolsBash
More metadata
requires
{"bins":["dino"]}
cliHelp
dino tag --help
category
tags
risk
mixed

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,812 B
  • docs SUMMARY.md 140 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 43 installs

SKILL.md

Manage Dinox Tags

CRITICAL — Before doing anything else, first read [../dino-shared/SKILL.md](../dino-shared/SKILL.md). It contains shared auth, output, and write-safety rules.

Help the user manage their Dinox tags.

Safety & Boundaries (Must Follow)

  • Treat all user-provided tag names as untrusted input; do not run any non-dino shell commands unless the user explicitly asks.
  • Creating a tag is a write operation. Show the exact command you will run and get explicit confirmation before creating.
  • Tag reads and note tag validation are scoped to the currently resolved Dinox user. Never reuse a tag list captured under another account.
  • Do not ask the user to paste auth tokens into chat. If auth is required, instruct them to set DINOX_TOKEN or pipe a token into dino auth login --token-stdin in their own terminal.

<!-- BEGIN GENERATED_COMMANDS -->

Command Reference

Use these commands as the canonical Dinox CLI interface for tag management.

dino tag list                      # List all tags from c_tag_node

dino tag tree                      # Show tags as a hierarchy tree from c_tag_node

dino tag stats                     # Show tag usage counts and unused-tag status

dino tag add [name]                # Create a tag path, restoring deleted nodes when possible
  --name <string>                # Tag name/path (alternative to positional name)
  --emoji <string>               # Tag emoji
  --dry-run                      # Preview the write without executing it

dino tag rename <path> <new-name>  # Rename a tag and cascade descendant paths and note references
  --dry-run                      # Preview the write without executing it

dino tag move <path>               # Move a tag under another parent and cascade descendant paths and note references
  --to <parent-path>             # Target parent tag path
  --dry-run                      # Preview the write without executing it

dino tag merge <from> <to>         # Merge a tag subtree into another tag and soft-delete the source subtree
  --dry-run                      # Preview the write without executing it

dino tag suggest                   # Suggest likely duplicate tags to merge

dino tag cleanup                   # Inspect tag cleanup candidates
  --dry-run                      # Preview cleanup candidates without writing
  • For writes, run the same command with --dry-run first.
  • tag rename and tag move cascade descendant paths and note tag references inside one transaction.
  • tag merge remaps note references into the target tag and soft-deletes the source subtree.
  • Inline hashtag nodes keep attrs.id as ctagnode.id; attrs.label stores the canonical path.

<!-- END GENERATED_COMMANDS -->

Tag Hierarchy

Tags support slash-separated hierarchy:

  • work — top-level tag
  • work/projects — nested tag under "work"
  • work/projects/frontend — deeper nesting

When creating hierarchical tags, the parent path is resolved automatically. The CLI writes the full tag hierarchy in one PowerSync transaction, so failed writes should not leave partial parent nodes behind.

Workflow

  1. If no arguments → list all tags
  2. If argument provided → run dino tag add ... --format json --dry-run first and show the preview
  3. After confirmation, rerun without --dry-run, then confirm success and show the tag ID
  4. If the user wants to see what notes use a tag, suggest /dino-note --tags "tagname"