mcpbeat

Tasx

vicnaum/tasx

File-based task tracker for projects: tasks live as markdown files in a tasks/ folder, state = folder location (root = inbox, in-progress/, waiting/, done/, cancelled/, decisions/ for open choices), agents manage tasks by moving the files; plus a zero-dependency local board UI (tasx serve) where the user changes states, answers decisions, and leaves comments that are written straight back into the md files and nudge the owning agent via agent-chat. Use when: (1) the user asks to set up / init a task tracker or tasks folder in a project, (2) the user or agent needs to create, list, move, complete, cancel, or comment on tasks in a repo that has a tasks/ folder, (3) the user asks 'what's in progress', 'what needs me', 'what's stale', or wants a task board / dashboard served, (4) starting a work session in a repo with tasks/ (run tasx doctor and reconcile), (5) a task is blocked on the user's feedback or on a decision — file it as waiting/ or a decision instead of asking and losing the thread, (6) generalizing/migrating older ad-hoc task folders (myhdd-style) onto the shared convention. Triggers on: tasks folder, task tracker, task board, tasx, kanban, what's in progress, needs my feedback, stale tasks, task dashboard.

13k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
51
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/vicnaum/vics-agent-skills --skill tasx

How to use it

Copy the folder

Take vicnaum/tasx from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.