shell-analyzer
Skill3 starsChanged 8 months agoApache-2.0View on GitHub
Run shell commands and analyze output with validated summaries. Use for build logs, test output, or any command with substantial output. Protects context by returning concise summaries with grep-validated citations.
In this repository8 other files it gives its agents.
- codebase-ripperSkill
- coding-toolsSkill
- create-gifSkill
- flatmachine-managerSkill
- openai-deep-research-citation-fixerSkill
- quick-reportSkill
- search-refinerSkill
- website-scraperSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
Run immediately with the shell command to execute:
- Very specific: line 14
Use --style=<style> to control output verbosity:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run immediately with the shell command to execute:
$HOME/.agents/skills/shell-analyzer/run.sh "<command>"Output Styles
Use --style=<style> to control output verbosity:
| Style | Description | Use Case |
compact | Brief summary + key findings (default) | General use |
minimal | Single line status | Quick checks |
detailed | Full markdown sections | Debug/investigation |
errors-only | Only output if problems found | CI/build monitoring |
Examples
# Default compact style
run.sh "npm run build"
# Minimal - just pass/fail
run.sh --style=minimal "cargo test"
# Detailed - full analysis
run.sh --style=detailed "pytest -v"
# Errors only - silent on success
run.sh --style=errors-only "make check"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.