agentleFS
Sign inStart free
Surya8991Surya8991/AgentMaster/skills/task-viewer/SKILL.md

task-viewer

Skill2 starsChanged 9 days agoMITView on GitHub

Use when the user wants to open, launch, start, or view the Claude Code task dashboard / Kanban board — a live web UI showing tasks across sessions (pending / in-progress / completed), dependencies, timeline, and activity. Wraps the standalone claude-task-viewer Express app. Not for creating or editing tasks (Claude Code owns task state); this only observes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $CFG is missing or $APP_DIR doesn't contain server.js, tell the user the app isn't installed/registered and ask for its path, then write …

    line 27
  2. Very specific:

    Default (no arg) or start:

    line 32
  3. Very specific:

    Read $APP_DIR as above.

    line 33
  4. Very specific:

    Ensure deps exist: if $APP_DIR/node_modules is missing, run npm install in $APP_DIR first.

    line 34
  5. Very specific:

    Start the server in the background and open the browser: PORT=<port-if-given> node "$APP_DIR/server.js" --open

    line 35
  6. Very specific:

    Default port is 3456; it auto-increments if busy (unless PORT is set).

    line 37
  7. Distinctive:

    Run it as a background process so it keeps serving after this turn.

    line 38

≈ “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

Launches and manages the claude-task-viewer dashboard — a real-time Kanban board that reads ~/.claude task JSON and serves it in the browser. Observation only: Claude Code controls task state, this just visualizes it.

Resolve the app directory

The app lives outside ~/.claude/skills (it's a full Node app, not a skill). Its location is stored in a config file so this skill stays portable:

CFG="$HOME/.claude/.agentmaster-cache/task-viewer.path"
APP_DIR="$(cat "$CFG" 2>/dev/null)"

If $CFG is missing or $APP_DIR doesn't contain server.js, tell the user the app isn't installed/registered and ask for its path, then write it back: printf '%s' "<path>" > "$CFG". Do not guess absolute paths.

Commands

Default (no arg) or start:

  1. Read $APP_DIR as above.
  2. Ensure deps exist: if $APP_DIR/node_modules is missing, run npm install in $APP_DIR first.
  3. Start the server in the background and open the browser: PORT=<port-if-given> node "$APP_DIR/server.js" --open
    • Default port is 3456; it auto-increments if busy (unless PORT is set).
    • Run it as a background process so it keeps serving after this turn.
  4. Report the URL it printed (http://localhost:<port>).

status: curl -s -o /dev/null -w '%{http_code}' http://localhost:3456 (try the reported port) — 200 means running.

stop: kill the running server process.

  • Windows: taskkill //F //IM node.exe is too broad — prefer finding the PID bound to the port. If unsure, tell the user which PID/port and let them confirm.
  • Unix: pkill -f "server.js" scoped to this app.

Notes

  • The viewer reads task data from $CLAUDE_DIR (defaults to ~/.claude). Override with CLAUDE_DIR=<path> or --dir <path> if the user keeps tasks elsewhere.
  • It's read-only over tasks; never claim it can create/modify/delete task state on Claude's behalf.
  • This is a long-running server. Don't block the conversation waiting on it — start it detached and move on.

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