slow-command-running
Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning
Best use case
slow-command-running is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning
Teams using slow-command-running should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/slow-command-running/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How slow-command-running Compares
| Feature / Agent | slow-command-running | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Pipe long running commands through tee(1) to allow watching output and repeated analyses without rerunning
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Command Output Logging ## When to use this skill Use it whenever running commands that: - are slow or long-running or expensive in any way - are likely to need multiple analyses of their output - involve API calls or other network operations - are GitHub CLI commands (`gh`) or similar ## How it works Always pipe these commands through `tee(1)` to capture output to a file while still displaying it in real-time. ## Key Principles - Never blindly pipe through `head(1)` unless you're sure premature termination via SIGPIPE won't cause problems. - When tee-ing into a temporary logfile, prefer the `tmp/` subdirectory of the repository rather than `/tmp`, so that you don't have to ask permission for access to `/tmp`. - Don't assume `tmp/` exists - you might need to create it first. ## Usage 1. Create `tmp/` directory if it doesn't exist: `mkdir -p tmp/` 2. Run the command with tee: `command | tee tmp/output.log` 3. The user can now choose to monitor that log file as it runs. 4. If you subsequently need to examine the output multiple times, reading from the log file prevents needing to re-run the slow command each time. ## Examples ```bash # Run tests with logging mkdir -p tmp/ npm test | tee tmp/test-output.log # Check GitHub action run mkdir -p tmp/ gh run view 12345 | tee tmp/action-run-12345.log # Access some API mkdir -p tmp/ some-API-call-command | tee tmp/logs.log ```
Related Skills
test-running
Run tests according to repository guidelines. Use after linting passes, before staging changes.
allow-agent-commands
Add or change allowed commands in AI agent permission configs (OpenCode, Claude Code)
agent-command-authoring
Create Claude Code slash commands, OpenCode command files, and Pi prompt templates that delegate to the right subagent or skill. Use when creating new commands or refactoring existing ones to follow platform conventions.
xlsx-to-csv
Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.
xero-mcp
Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
xero-browser
General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
task-orchestration
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
task-implementation
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
task-generation
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.
subagent-authoring
Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.
skill-authoring
Create and maintain Claude Code skills following Anthropic best practices. Use when building new skills, refactoring existing ones, or ensuring skills follow official guidelines for structure, naming, progressive disclosure, and testing.
safe-rm
Safely delete files / directories without asking for permission