Tiki Management

VerifiedCaution

Manages tikis, Markdown files in .doc/tiki with frontmatter (type, status, priority). Allows viewing, creating, updating, and deleting tikis, tracking authors via Git. Useful for lightweight issue management embedded in the project.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude Code
#tiki#ticket-management#markdown#git-integration#task-tracking

Recommended for

Our review

This skill manages tickets (tikis) as markdown files stored in `.doc/tiki` directory, with CRUD operations and git tracking.

Strengths

  • Leverages simple markdown files that are naturally version-controlled with git.
  • Structured metadata (type, status, priority, points) via frontmatter.
  • Automates git operations (add, rm) to keep the repository consistent.
  • Tracks authorship and changes through git history.

Limitations

  • Does not support multi-user management without git conflicts.
  • No graphical interface; all operations are text-based.
  • Attachments are only markdown links, not integrated storage.
When to use it

Use this skill to manage a lightweight ticket backlog in a project where all contributors are using Claude Code and git.

When not to use it

Avoid this skill if you need a collaborative ticket tracker with Kanban boards or real-time notifications.

Security analysis

Caution
Quality score88/100

The skill uses git commands for adding and removing files. Although intended for a specific directory, the wildcard permissions mean it could potentially affect other files if the skill is misled. No destructive shell commands like rm -rf or curl are included, but git rm is a destructive action on tracked files, hence caution.

Findings
  • Bash(git add:*) and Bash(git rm:*) allow the skill to stage any file for addition or deletion, not limited to the .doc/tiki directory by tool constraints. While the skill instructs to only operate on tiki files, there is no enforcement mechanism, so a misdirection could lead to unintended file deletions or staging.

Examples

Create a new tiki
Create a new tiki for a bug fix: the login button is not working. Type: bug, priority: high (1), points: 3.
Update tiki status
Set TIKI-X7F4K2 to in progress.
Show tiki details
Show me the details of TIKI-ABC123, including who created it and when.

name: tiki description: view, create, update, delete tikis allowed-tools: Read, Grep, Glob, Update, Edit, Write, WriteFile, Bash(git add:), Bash(git rm:)

tiki

A tiki is a Markdown file in tiki format saved in the project .doc/tiki directory with a name like tiki-abc123.md in all lower letters. IMPORTANT! files are named in lowercase always If this directory does not exist prompt user for creation

tiki ID format

ID format: TIKI-ABC123 where ABC123 is 6-char random alphanumeric Derived from filename, NOT stored in frontmatter

Examples:

  • Filename: tiki-x7f4k2.md → ID: TIKI-X7F4K2

tiki format

A tiki format is Markdown with some requirements:

frontmatter

---
title: My ticket
type: story
status: backlog
priority: 3
points: 5
tags:
  - markdown
  - metadata
---

where fields can have these values:

  • type: bug, feature, task, story, epic
  • status: backlog, ready, in_progress, review, done
  • priority: is any integer number from 1 to 5 where 1 is the highest priority. Mapped to priority description:
    • high: 1
    • medium-high: 2
    • medium: 3
    • medium-low: 4
    • low: 5
  • points: story points from 1 to 10

body

The body of a tiki is normal Markdown

if a tiki needs an attachment it is implemented as a normal markdown link to file syntax for example:

Describe

When asked a question about a tiki find its file and read it then answer the question If the question is who created this tiki or who updated it last - use the git username For example:

  • who created this tiki? use git log --follow --diff-filter=A -- <file_path> to see who created it
  • who edited this tiki? use git blame <file_path> to see who edited the file

View

Created timestamp is taken from git file creation if available else from the file creation timestamp.

Author is taken from git history as the git user who created the file.

Creation

When asked to create a tiki:

  • Generate a random 6-character alphanumeric ID (lowercase letters and digits)
  • The filename should be lowercase: tiki-abc123.md
  • If status is not specified use backlog
  • If priority is not specified use 3
  • If type is not specified - prompt the user or use story by default

Example: for random ID x7f4k2:

  • Filename: tiki-x7f4k2.md
  • tiki ID: TIKI-X7F4K2

Create from file

if asked to create a tiki from Markdown or text file - create only a single tiki and use the entire content of the file as its description. Title should be a short sentence summarizing the file content

git

After a new tiki is created git add this file. IMPORTANT - only add, never commit the file without user asking and permitting

Update

When asked to update a tiki - edit its file For example when user says "set TIKI-ABC123 in progress" find its file and edit its frontmatter line from status: backlog to status: in progress

git

After a tiki is updated git add this file IMPORTANT - only add, never commit the file without user asking and permitting

Deletion

When asked to delete a tiki git rm its file If for any reason git rm cannot be executed and the file is still there - delete the file

Implement

When asked to implement a tiki and the user approves implementation change its status to review and git add it

Related skills