一键导入
status
Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide for safely discovering and installing skills from external repositories. Use when a user asks for something where a specialized skill likely exists (browser testing, PDF processing, document generation, etc.) and you want to bootstrap your understanding rather than starting from scratch.
Connect to MCP (Model Context Protocol) servers and create skills for repeated use. Load when a user wants to use an MCP server, connect to external tools via MCP, or when they mention MCP, model context protocol, or specific MCP servers.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations.
Decomposes and reorganizes agent memory blocks into focused, single-purpose components. Use when memory has large multi-topic blocks, redundancy, or poor organization.
Comprehensive guide for initializing or reorganizing agent memory. Load this skill when running /init, when the user asks you to set up your memory, or when you need guidance on creating effective memory files.
Send messages to other agents on your server. Use when you need to communicate with, query, or delegate tasks to another agent.
| name | status |
| description | Generate a status report across all workstreams using beads issue tracking. Shows active work, blockers, and available tasks. |
| argument-hint | |
| user-invocable | true |
| allowed-tools | Bash |
Generate a comprehensive status report by running these commands:
!bd stats 2>/dev/null || echo "No beads stats available"
!bd list --status=in_progress 2>/dev/null || echo "No in-progress issues"
!bd blocked 2>/dev/null || echo "No blocked issues"
!bd ready 2>/dev/null || echo "No ready issues"
Summarize findings in this format:
[List in-progress issues with assignees]
[List blocked issues and what they're waiting on]
[List ready issues that can be picked up]
[Stats summary — open/closed/blocked counts]
[Suggested next actions based on current state]