agentleFS
Sign inStart free
apappascsapappascs/claude-code-sessions/skills/session-tasks/SKILL.md

session-tasks

Skill2 starsChanged 26 days agoMITView on GitHub

Aggregates tasks across Claude Code task lists and sessions — shows pending, in-progress, and completed tasks with dependencies. Use when the user asks "what tasks are pending", "show my tasks", "orphaned tasks", "task dependencies", or wants a cross-session task inventory.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    If tasks have blocks/blockedBy relationships, show a dependency summary:

    line 54

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

Session Tasks

Aggregate tasks from the Tasks filesystem (~/.claude/tasks/) and session JSONL.

List all task lists

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts task-lists

All tasks across all task lists

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --format json

Filter by status

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --status pending --format json
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --status in_progress --format json

Tasks from a specific task list

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts tasks --task-list <task-list-id> --format json

Fallback: tasks from a session JSONL (legacy)

bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-parser.ts tasks <session-jsonl-path>

Present results

Group tasks by status:

  1. In Progress tasks first (actively being worked on — check activeForm for current activity)
  2. Pending tasks (need attention — check blockedBy for dependencies)
  3. Completed tasks

For each task show: subject, description, status, task list ID, dependencies.

If tasks have blocks/blockedBy relationships, show a dependency summary:

  • "Task 2 (Add tests) is blocked by Task 1 (Setup project)"

Flag orphaned tasks — tasks with status "pending" or "in_progress" in task lists older than 7 days.

The source field indicates whether the task came from the filesystem ("filesystem") or was extracted from session JSONL ("jsonl").

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