Full Tasuku Context Dump

VerifiedSafe

Retrieves complete project state including all tasks, learnings, and decisions. Use with /tk:context or when user requests full context overview.

Sby Skills Guide Bot
ProductivityBeginner
306/2/2026
Claude Code
#tasuku#context-dump#task-management#project-state

Recommended for

Our review

Dumps the full Tasuku context (tasks, learnings, decisions, notes) for agent consumption to understand the project state.

Strengths

  • Provides a structured, scannable overview of the project
  • Highlights in-progress, blocked, and priority tasks
  • Includes recent decisions and learned rules

Limitations

  • Requires the tk_context MCP tool to be set up
  • Can be large for very busy projects
  • Archived tasks are skipped unless explicitly requested
When to use it

At the start of a session to quickly reorient yourself with the project state.

When not to use it

When only partial or specific information is needed (a targeted query is better).

Security analysis

Safe
Quality score75/100

The skill only instructs to call an MCP tool to retrieve project state and present it in a structured format. There are no destructive commands, no data exfiltration, and no obfuscation. No external network calls or system modifications are made beyond the intended context retrieval.

No concerns found

Examples

Full context request
Can you show me the full Tasuku context including all tasks, learnings, decisions, and notes?
Shortcut trigger
/tk:context

name: tk-context description: Dump full Tasuku context for agent consumption. Use when user says /tk:context or asks for full context, project state, or needs to understand the entire task landscape.

Full Context Dump

Provide complete project context including all tasks, learnings, decisions, and notes.

Instructions

  1. Use the tk_context MCP tool to get the full .tasuku.json state
  2. Present the information in a structured, scannable format
  3. Highlight key items:
    • Tasks currently in progress (what's being worked on)
    • Blocked tasks and their blockers
    • Recent decisions that affect current work
    • Relevant learnings/rules

Output Format

## Current Work
[List in_progress tasks with owner if set]

## Ready Queue
[List ready tasks sorted by priority]

## Blockers
[List blocked tasks and what's blocking them]

## Key Decisions
[Recent or relevant architectural decisions]

## Learnings & Rules
[Important insights, especially any marked as rules]

## Notes
[Any notes attached to active tasks]

Notes

  • This is meant for getting oriented at the start of a session
  • Focus on actionable information
  • Skip archived tasks unless specifically requested
  • If context is large, summarize done tasks as a count
Related skills