check-logs
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
Fetch and summarize recent logs for a service from the right provider.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- NVIDIA/kumo-enginetheir own version, first seen Oct 20, 2026
- SolaceProducts/solace-broker-mcptheir own version, first seen Jul 23, 2026
- Conzel/personal-claude-code-skillstheir own version, first seen Apr 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- NVIDIA/kumo-engine★ 78same name
- SolaceProducts/solace-broker-mcp★ 18same name
- Conzel/personal-claude-code-skills★ 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 repository8 other files it gives its agents.
- deployment-statusSkill
- deploy-serviceSkill
- investigate-outageSkill
- provision-supabaseSkill
- restart-serviceSkill
- review-local-repoSkill
- rollback-deploySkill
- set-env-varsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If the operator named a provider explicitly, use it.
- Distinctive: line 30
Read-only. Redact any secrets that appear in log lines.
“Common” is measured: kept by at least 6 in 10 of the 3 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
When to use
The operator asks for logs ("show the last 20 logs", "give me top logs for both", "tail aethos-ui").
Steps
- Resolve provider + target from the prompt or active context. Quantifiers like "both"/"them"/"those" mean the entities from the previous turn (e.g. both Railway services) — never a literal project name.
- If the operator named a provider explicitly, use it. If there is no provider and no context, ask which provider/target.
- Fetch the requested number of recent log lines (default a small N) for each resolved target.
- Summarize: surface errors/warnings first, include timestamps, and note if logs are stale relative to the last deploy/restart.
Readonly tools
- provider_logs
- recall_last_deployment_thread
Governance
Read-only. Redact any secrets that appear in log lines.
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.