Google Sheets
Read, write, and manage Google Sheets spreadsheets
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Read, write, and manage Google Sheets spreadsheets
Check bundled source handbook files for capability, policy, or implementation verification questions. Use when users ask to double-check or verify what the internal/source handbook says.
Recover, export, or summarize recent human and assistant conversations from local agent session stores while excluding tool calls, reasoning, system injection, copied parent history, and subagent noise. Use for recent-session inventories, clean conversation recovery, or topic summaries from tree-shaped `.claude` and rollout-shaped `.codex` JSONL stores on Linux or macOS.
Summarizes an stlinspector InspectionReport (JSON) for a non-technical stakeholder. Use when asked to "summarize", "explain", or "triage" an inspection report.
Produce proof-of-execution demos of the Packmind CLI (`packmind-cli`) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR. Renders a crisp master SVG and rasterizes it to a PNG — the PNG is what you embed, because GitHub does not render SVG in PR/issue bodies. Use this whenever a dev task touches the CLI — new command, changed output, new flag, bug fix in terminal rendering — and the PR would benefit from showing the tool actually running. Trigger it when the user says "record a CLI demo", "show the command output", "add a terminal screenshot to the PR", "prove the CLI works", "capture the CLI", "demo the command", or whenever you finish CLI work and are about to open or update a PR. Default to running this for any PR whose diff includes CLI source, even if the user didn't explicitly ask for a screenshot — a CLI PR without a visual of the output is an incomplete deliverable.
Record polished UI demo videos and screenshots of a running web app using Playwright MCP — for client deliverables, release notes, feature walkthroughs, or bug repros. Produces an HD WebM video with chapter markers, a mandatory animated cursor overlay, and a mandatory subtitle bar that narrates each step (positioned deliberately so it never masks the UI being demonstrated), plus full-page screenshots at each step. Use this whenever the user asks to "record a demo", "create a screencast", "make a UI walkthrough video", "document this feature with video", "show the client how X works", "capture screenshots of the app", or anything similar — even when the user only says "make a video" or "take screenshots" in the context of a running frontend. Also use it when the user wants to demonstrate a workflow, generate marketing-quality footage of an app, or produce repeatable visual documentation.
Query, lint, ingest, author, and manage TradingCodex Knowledge Wikis. Use for company, product, technology, material, process, scientific, industry, or value-chain background knowledge; requests such as ‘put this in the Wiki’ or ‘promote reusable knowledge from the recent Artifact’; Obsidian-compatible Wiki maintenance; or community `knowledge-wiki-*` package validation and lifecycle management. Wiki writes require an explicit user request, while relevant Wiki reads may happen automatically.
Use when a user asks for Yellowstone National Park sound recordings, YSL route data, public field-recording examples, or a playable Yellowstone sound archive.
接收原始语料,进行中文逻辑重构,严格按照当前 Obsidian 模板格式化并写入文件。
Process multiple documents in bulk with parallel execution