Liveblog Dev
liveblog/liveblog
Run a local Liveblog development environment. An agent skill from liveblog/liveblog.
Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream.
Install Tailing Build Output
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-output --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/tailing-build-output .claude/skills/tailing-build-output && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .claude/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-outputType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-output --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/tailing-build-output .agents/skills/tailing-build-output && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .agents/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-output --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/tailing-build-output .cursor/skills/tailing-build-output && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .cursor/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/spencerpauly/awesome-cursor-skills.git --path resources/tailing-build-output--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-output --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/tailing-build-output .gemini/skills/tailing-build-output && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .gemini/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-outputInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/tailing-build-output .github/skills/tailing-build-output && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .github/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills tailing-build-output --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/tailing-build-output .opencode/skills/tailing-build-output && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tailing-build-output" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/tailing-build-output into .opencode/skills/tailing-build-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tailing-build-output", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tailing-build-output- GitHub stars
- 844
- Token cost
- ~524 tokens
- SKILL.md length
- 235 words
- Files
- 1
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- CC0-1.0
At a glance
Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream.
- Works in 4 steps: Start or Find the Build → Poll for Output → Fix Errors in Flight → …
- Tasks that involve Containers
- SKILL.md covers Workflow and Tips
- Calls turbo, npm and pnpm
What it does
Tailing Build Output is an agent skill from spencerpauly/awesome-cursor-skills. Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes.
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers. It works with Docker and webpack. The repository describes itself as: A curated list of awesome skills for Cursor. The licence is CC0-1.0.
When your agent uses it
- Tasks that involve Containers
Example prompts
- “/tailing-build-output”
Requirements
- Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 99cd265. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
turbonpmpnpmdocker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, pnpm and docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tailing Build Output loads about 524 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 235 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from spencerpauly/awesome-cursor-skills at commit 99cd265, republished under its CC0-1.0 licence (© spencerpauly). 235 words, ~524 tokens.
Download SKILL.mdSave it as
.claude/skills/tailing-build-output/SKILL.md (or your agent's skills folder).- name
- tailing-build-output
- description
- Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Summarize issues and fix them before the build finishes.
- user-invocable
- true
Tailing Build Output
Watch a build process in real time via terminal files and fix issues as they appear.
Workflow
1. Start or Find the Build
Either start the build yourself or find the terminal running it:
head -n 10 <terminals_folder>/*.txtLook for commands like npm run build, pnpm build, turbo build, docker build, tsc, vite build.
2. Poll for Output
Read the terminal file periodically. Look for:
Errors (fix immediately):
ERROR/Error:/error TSModule not found/Cannot find moduleSyntaxError/TypeErrorFailed to compile
Warnings (collect for summary):
WARNING/Warning:/warnDeprecation/deprecated- Unused imports/variables
- Large bundle size warnings (
asset size limit)
Progress indicators:
- Webpack:
[XX%],modules,chunks - Turbo: task completion logs
- Docker:
Step X/Y - TypeScript: file count
3. Fix Errors in Flight
When an error appears:
- Extract the file path and line number from the error
- Read and fix the source file
- If the build supports watch mode, it will re-trigger automatically
- If not, note the fix and let the build continue — it may reveal more errors
4. Summary Report
After the build completes (check for exit_code in terminal footer):
Build Summary:
Status: Failed (exit code 1) / Succeeded
Duration: ~45s
Errors fixed: 3
Remaining warnings: 2
- Large bundle: src/pages/Dashboard.tsx (450kb)
- Deprecated API: useRouter from 'next/router'Tips
- Don't fix warnings during the build — collect them and address after
- For
turbo build, errors may appear in parallel task output — check all task logs - Docker builds cache layers — if you fix a file early in the Dockerfile, later layers rerun
- TypeScript's
--noEmitis useful for type-checking without a full build
© spencerpauly, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in resources/tailing-build-output of spencerpauly/awesome-cursor-skills.
Open the folder on GitHubat commit 99cd265
Compare with similar skills
Tailing Build Output next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tailing Build Output this skillspencerpauly/awesome-cursor-skills | 844 | — | ~524 | Automated safety check: Pass | CC0-1.0 | |
| Liveblog Devliveblog/liveblog | 119 | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.5k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 16k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
Ssh Skill
badseal/ssh-skill
A skill your agent uses when a task requires SSH or SCP/SFTP behavior, a remote server, server alias/IP/hostname/user@host, bastion or jump-host access, remote command execution, upload/download…
More from spencerpauly/awesome-cursor-skills
All 60 skills in this repoGenerating Images
spencerpauly/awesome-cursor-skills
Generate or edit images using the OpenAI Image API (gpt-image-2).
Babysitting PR
spencerpauly/awesome-cursor-skills
Monitor a pull request for CI failures, review comments, and merge conflicts — then fix them automatically.
Best Of N Solving
spencerpauly/awesome-cursor-skills
Solve a hard problem by trying multiple approaches in parallel using isolated git worktrees.
Grinding Until Pass
spencerpauly/awesome-cursor-skills
Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean.
Parallel CI Triage
spencerpauly/awesome-cursor-skills
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.
Parallel Exploring
spencerpauly/awesome-cursor-skills
Explore a large codebase in parallel by launching multiple explore subagents that each investigate a different area simultaneously.
Related
Categories
Questions about Tailing Build Output
What does Tailing Build Output do?
Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream. Tailing Build Output is an agent skill from spencerpauly/awesome-cursor-skills. Monitor a build process (webpack, turbo, docker) for warnings and errors as they stream.
When should I use Tailing Build Output?
Tailing Build Output fits situations like: tasks that involve Containers.
How do I install Tailing Build Output in Claude Code?
Run `npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a claude-code`. Or copy the skill folder (resources/tailing-build-output in spencerpauly/awesome-cursor-skills) into .claude/skills/tailing-build-output in your project. Claude Code loads it when a task matches its description.
How do I install Tailing Build Output in Codex?
Run `npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a codex`. Or copy the skill folder (resources/tailing-build-output in spencerpauly/awesome-cursor-skills) into .agents/skills/tailing-build-output in your project. Codex loads it when a task matches its description.
Can I use Tailing Build Output in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spencerpauly/awesome-cursor-skills --skill tailing-build-output -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tailing-build-output, .gemini/skills/tailing-build-output, .github/skills/tailing-build-output and .opencode/skills/tailing-build-output in your project.
What does Tailing Build Output need to run?
Going by SKILL.md and its folder, Tailing Build Output needs the command-line tools its instructions call (turbo, npm, pnpm and docker). Our summary lists: Docker.
Does Tailing Build Output access the network?
SKILL.md contains no URLs. Its commands use npm and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Tailing Build Output safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Tailing Build Output use?
Tailing Build Output is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tailing Build Output use?
About 524 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tailing Build Output?
Skills that share tags, products or a category with Tailing Build Output: Liveblog Dev (liveblog/liveblog, 119 stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tailing Build Output?
spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 844 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on August 2, 2026.
Source: spencerpauly/awesome-cursor-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.