LangBot Plugin Development
langbot-app/LangBot
Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.
Watch running terminal processes for crashes and stack traces.
Install Monitoring Terminal Errors
$ npx skills add spencerpauly/awesome-cursor-skills --skill monitoring-terminal-errors -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills monitoring-terminal-errors --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/monitoring-terminal-errors .claude/skills/monitoring-terminal-errors && 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 "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .claude/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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/monitoring-terminal-errorsType 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 monitoring-terminal-errors -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills monitoring-terminal-errors --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/monitoring-terminal-errors .agents/skills/monitoring-terminal-errors && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .agents/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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 monitoring-terminal-errors -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills monitoring-terminal-errors --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/monitoring-terminal-errors .cursor/skills/monitoring-terminal-errors && 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 "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .cursor/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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/monitoring-terminal-errors--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 monitoring-terminal-errors -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install spencerpauly/awesome-cursor-skills monitoring-terminal-errors --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/monitoring-terminal-errors .gemini/skills/monitoring-terminal-errors && 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 "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .gemini/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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 monitoring-terminal-errorsInstalls 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 monitoring-terminal-errors -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/monitoring-terminal-errors .github/skills/monitoring-terminal-errors && 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 "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .github/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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 monitoring-terminal-errors -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 monitoring-terminal-errors --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/monitoring-terminal-errors .opencode/skills/monitoring-terminal-errors && 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 "monitoring-terminal-errors" agent skill from https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/monitoring-terminal-errors into .opencode/skills/monitoring-terminal-errors/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitoring-terminal-errors", 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
monitoring-terminal-errors- GitHub stars
- 842
- Token cost
- ~561 tokens
- SKILL.md length
- 277 words
- Files
- 1
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- CC0-1.0
At a glance
Watch running terminal processes for crashes and stack traces.
- Works in 5 steps: Identify the Terminal → Read Terminal Output → Extract the Source Location → …
- Tasks that involve Debugging
- SKILL.md covers Workflow and Tips
- Calls npm, pnpm and python
What it does
Monitoring Terminal Errors is an agent skill from spencerpauly/awesome-cursor-skills. Watch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically.
Its SKILL.md is about 560 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 Development, covering Debugging. It works with Python. 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 Debugging
Example prompts
- “/monitoring-terminal-errors”
Requirements
- Python 3
- Node.js
Workflow steps
5 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:
npmpnpmpython
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and pnpm, 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
Monitoring Terminal Errors loads about 561 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 277 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). 277 words, ~561 tokens.
Download SKILL.mdSave it as
.claude/skills/monitoring-terminal-errors/SKILL.md (or your agent's skills folder).- name
- monitoring-terminal-errors
- description
- Watch running terminal processes for crashes and stack traces. When an error appears, navigate to the failing file and line, diagnose, and fix it automatically.
- user-invocable
- true
Monitoring Terminal Errors
Continuously watch a running process (dev server, test runner, build) for errors and fix them as they appear.
Workflow
1. Identify the Terminal
List terminal files and find the one running the target process:
head -n 10 <terminals_folder>/*.txtLook for terminals running dev servers (npm run dev, pnpm dev, python manage.py runserver, etc.).
2. Read Terminal Output
Read the full terminal file content. Search for error patterns:
- Stack traces:
at <function> (<file>:<line>:<col>) - Node.js:
Error:,TypeError:,ReferenceError:,ENOENT,ECONNREFUSED - Python:
Traceback (most recent call last):followed byFile "<path>", line <n> - React/Next.js:
Unhandled Runtime Error,Error: ...,Module not found - Build errors:
ERROR in,Failed to compile,SyntaxError - Vite:
[vite] Internal server error: - TypeScript:
error TS\d+:
3. Extract the Source Location
From the stack trace, extract:
- File path
- Line number
- Error message
For Node.js: at functionName (/path/to/file.ts:42:10)
For Python: File "/path/to/file.py", line 42, in function_name
4. Navigate and Fix
- Read the identified file around the error line
- Understand the error (missing import, type mismatch, undefined variable, etc.)
- Apply the fix
- Re-read the terminal file to confirm the server recovered (hot reload should pick it up)
5. Loop
If the server is still showing errors after the fix, repeat from step 2. Stop when:
- The terminal shows a clean "compiled successfully" or equivalent
- No new errors appear in the output
- You've made 5 attempts without resolution (report to user)
Tips
- Check for
exit_codein the terminal file footer — if present, the process has crashed entirely and needs a restart - Some errors cascade — fix the first/root error and the rest often disappear
- For HMR errors, the fix might just be saving the file again to trigger a rebuild
© 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/monitoring-terminal-errors of spencerpauly/awesome-cursor-skills.
Open the folder on GitHubat commit 99cd265
Compare with similar skills
Monitoring Terminal Errors 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 |
|---|---|---|---|---|---|---|
| Monitoring Terminal Errors this skillspencerpauly/awesome-cursor-skills | 842 | — | ~561 | Automated safety check: Pass | CC0-1.0 | |
| LangBot Plugin Developmentlangbot-app/LangBot | 18k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Python Performance Optimizationwshobson/agents | 40k | 13 repos | ~814 | Automated safety check: Pass | MIT | |
| Git History Bug Auditben-manes/caffeine | 18k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Keybase RPC Log Analysiskeybase/client | 9.3k | — | ~3k | Automated safety check: Pass | BSD-3-Clause | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 |
Similar skills
Python Performance Optimization
wshobson/agents
Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.
Git History Bug Audit
ben-manes/caffeine
Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.
Keybase RPC Log Analysis
keybase/client
Captures a clean Keybase service log and analyzes it for redundant, duplicated or looping RPCs, then checks whether a caching fix reduced the calls.
The Art of Debugging
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
More from spencerpauly/awesome-cursor-skills
All 57 skills in this repoBabysitting 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.
Profiling Performance
spencerpauly/awesome-cursor-skills
Profile a running web application's CPU performance using Cursor's built-in browser profiler.
Related
Works with
Categories
Questions about Monitoring Terminal Errors
What does Monitoring Terminal Errors do?
Watch running terminal processes for crashes and stack traces. Monitoring Terminal Errors is an agent skill from spencerpauly/awesome-cursor-skills. Watch running terminal processes for crashes and stack traces.
When should I use Monitoring Terminal Errors?
Monitoring Terminal Errors fits situations like: tasks that involve Debugging.
How do I install Monitoring Terminal Errors in Claude Code?
Run `npx skills add spencerpauly/awesome-cursor-skills --skill monitoring-terminal-errors -a claude-code`. Or copy the skill folder (resources/monitoring-terminal-errors in spencerpauly/awesome-cursor-skills) into .claude/skills/monitoring-terminal-errors in your project. Claude Code loads it when a task matches its description.
How do I install Monitoring Terminal Errors in Codex?
Run `npx skills add spencerpauly/awesome-cursor-skills --skill monitoring-terminal-errors -a codex`. Or copy the skill folder (resources/monitoring-terminal-errors in spencerpauly/awesome-cursor-skills) into .agents/skills/monitoring-terminal-errors in your project. Codex loads it when a task matches its description.
Can I use Monitoring Terminal Errors 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 monitoring-terminal-errors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitoring-terminal-errors, .gemini/skills/monitoring-terminal-errors, .github/skills/monitoring-terminal-errors and .opencode/skills/monitoring-terminal-errors in your project.
What does Monitoring Terminal Errors need to run?
Going by SKILL.md and its folder, Monitoring Terminal Errors needs the command-line tools its instructions call (npm, pnpm and python). Our summary lists: Python 3; Node.js.
Does Monitoring Terminal Errors access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Monitoring Terminal Errors 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 Monitoring Terminal Errors use?
Monitoring Terminal Errors 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 Monitoring Terminal Errors use?
About 561 tokens (SKILL.md is roughly 2.2k 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 Monitoring Terminal Errors?
Skills that share tags, products or a category with Monitoring Terminal Errors: LangBot Plugin Development (langbot-app/LangBot, 18k stars), Python Performance Optimization (wshobson/agents, 40k stars), Git History Bug Audit (ben-manes/caffeine, 18k stars) and Keybase RPC Log Analysis (keybase/client, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monitoring Terminal Errors?
spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 842 GitHub stars. The repository holds 57 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.