logs
Skill1 starsChanged 9 months agoMITView on GitHub
View and aggregate logs from various sources (systemd, docker, application files). Use when debugging, monitoring services, or investigating errors.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 163
If logs are empty:
- Very specific: line 164
Check if service is running: systemctl status $SERVICE
- Very specific: line 165
Check log rotation: ls -la /var/log/
- Very specific: line 166
Check Docker container status: docker ps -a
- Distinctive: line 167
Verify log file permissions
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Log Aggregator
View and search logs from multiple sources across your projects.
Arguments
$0: Service name or project (optional - shows all if not specified)$1: Options -error,warn,tail,search:pattern(optional)
Log Sources by Project
| Project | Source | Location/Command |
| eruditiontx-services-mvp | systemd | journalctl -u erudition-service |
| eruditiontx-services-mvp | app | ~/Projects/eruditiontx-services-mvp/logs/ |
| mathmatterstx-services | systemd | journalctl -u mathmatters-service |
| agila-tax-management | docker | docker logs agila-backend |
| notaryo.ph | Next.js | .next/ logs, terminal output |
| bocs-turbo | Vercel | vercel logs |
Commands
View Recent Logs
Systemd Services:
journalctl -u $SERVICE -n 100 --no-pager
# Follow mode
journalctl -u $SERVICE -fDocker Containers:
docker logs $CONTAINER --tail 100
# Follow mode
docker logs $CONTAINER -fApplication Log Files:
tail -n 100 ~/Projects/$PROJECT/logs/app.log
# Follow mode
tail -f ~/Projects/$PROJECT/logs/app.logFilter by Level
Errors Only:
# Systemd
journalctl -u $SERVICE -p err -n 100 --no-pager
# Docker/Files
docker logs $CONTAINER 2>&1 | grep -i "error\|exception\|traceback"
# Log files
grep -i "error\|exception\|traceback" ~/Projects/$PROJECT/logs/app.logWarnings:
grep -i "warn\|warning" $LOG_SOURCESearch Logs
# Search for pattern
journalctl -u $SERVICE | grep -i "$PATTERN"
docker logs $CONTAINER 2>&1 | grep -i "$PATTERN"
grep -i "$PATTERN" ~/Projects/$PROJECT/logs/*.logTime-Based Filtering
# Last hour
journalctl -u $SERVICE --since "1 hour ago"
# Today
journalctl -u $SERVICE --since today
# Specific time range
journalctl -u $SERVICE --since "2024-01-01 00:00:00" --until "2024-01-01 23:59:59"Log Aggregation Mode
View logs from multiple services at once:
# All Erudition services
journalctl -u erudition-service -u mathmatters-service -f
# All Docker containers
docker-compose logs -fLog Analysis
Count Errors by Type
grep -i "error" $LOG_FILE | sort | uniq -c | sort -rn | head -20Find Slow Requests
grep -E "took [0-9]+ms" $LOG_FILE | awk '{print $NF}' | sort -rn | head -10Track Request IDs
grep "$REQUEST_ID" $LOG_FILEOutput Format
Logs: [service-name]
Source: [systemd/docker/file]
Filter: [all/error/warn]
Time: [range]
---
[Formatted log entries with timestamps]
---
Summary:
- Total entries: X
- Errors: Y
- Warnings: Z
- Time span: [start] to [end]Common Log Patterns
FastAPI (Python)
INFO: 127.0.0.1:52847 - "GET /health HTTP/1.1" 200 OK
ERROR: Exception in route handler: [error message]Next.js
ready - started server on 0.0.0.0:3000
error - Error: [error message]
warn - [warning message]Docker
[timestamp] [level] [message]Troubleshooting
If logs are empty:
- Check if service is running:
systemctl status $SERVICE - Check log rotation:
ls -la /var/log/ - Check Docker container status:
docker ps -a - Verify log file permissions
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- F3-Nation/f3-nation★ 208same name
- SynchronetBBS/sbbs★ 111same name
- nitaybz/ginnie-agents★ 16same name
- vercel/vercel-deploy-claude-code-plugin★ 13same name
- apinizer/agentnizer-cookbook★ 2same name
- talayash/spring-fleet★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository125 other files it gives its agents.
- skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- address-sanitizerSkill
- aflppSkill
- algorand-vulnerability-scannerSkill
- algorithmic-artSkill
- ask-questions-if-underspecifiedSkill
- atherisSkill
- audit-context-buildingSkill
- audit-prep-assistantSkill
- autonomous-skillSkill
- aws-skillsSkill
- better-authSkill
- brainstormingSkill
- brand-guidelinesSkill
- burpsuite-project-parserSkill
- cairo-vulnerability-scannerSkill
- canvas-designSkill
- cargo-fuzzSkill
- changelog-generatorSkill
- claude-in-chrome-troubleshootingSkill
- cloudflare-skillsSkill
- code-maturity-assessorSkill
- codeqlSkill
- codex-skillSkill
- constant-time-analysisSkill
- constant-time-testingSkill
- cosmos-vulnerability-scannerSkill
- coverage-analysisSkill
- d3js-visualizationSkill
- db-resetSkill
- deep-researchSkill
- deploySkill
- dev-startSkill
- differential-reviewSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- doc-generateSkill
- documentationSkill
- docxSkill
- dwarf-expertSkill
- entry-point-analyzerSkill
- env-checkSkill
- executing-plansSkill
- expo-skillsSkill
- finishing-a-development-branchSkill
- firebase-apk-scannerSkill
- fix-reviewSkill
- frontend-designSkill
- fuzzing-dictionarySkill
- fuzzing-obstaclesSkill
- git-automationSkill
- google-design-mdSkill
- guidelines-advisorSkill
- harness-writingSkill
- health-checkSkill
- huggingface-skillsSkill
- insecure-defaultsSkill
- internal-commsSkill
- The first 60 shown.
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.

