logs
Skill115 starsChanged 9 days agoLicence not identifiedView on GitHub
Use when locating the right Synchronet log file or stream for a given question on Windows or *nix — the per-category files in `data/` (error/hack/spam/guru/hungup/crash/events/sbbsecho/sendmail/logon/csts.tab), the per-day Terminal Server logs in `data/logs/<date>.log`, the Web Server's HTTP access log, the server console (lprintf) stream and its routing to syslog/journalctl/console depending on daemon mode and init system, the sbbsctrl-on-Windows-only `data/logs/{TS,WS,MS,FS}*.LOG` trap, MQTT log subscription, multi-instance traps when sibling BBSes share `text/*.can`, and the `ip.can`/`ip-silent.can` field format. Trigger on "did the auto-filter fire?", "tail the web server log", "where do hack attempts go?", "subscribe to all logs across hosts", "decode an ip.can line", or "why doesn't WS<date>.LOG update on Linux?
6 other projects use a version of this.
Adopted by
Most recently taken up by
- allanninal/claude-code-skillstheir own version, first seen Oct 17, 2026
- F3-Nation/f3-nationtheir own version, first seen Oct 9, 2026
- talayash/spring-fleettheir own version, first seen Sep 29, 2026
- nitaybz/ginnie-agentstheir own version, first seen Aug 28, 2026
- apinizer/agentnizer-cookbooktheir own version, first seen Jul 21, 2026
- vercel/vercel-deploy-claude-code-plugintheir own version, first seen Dec 18, 2025
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★ 210same name
- nitaybz/ginnie-agents★ 16same name
- vercel/vercel-deploy-claude-code-plugin★ 13same name
- apinizer/agentnizer-cookbook★ 2same name
- talayash/spring-fleet★ 2same name
- allanninal/claude-code-skills★ 1same 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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- exec/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- xtrn/CLAUDE.mdCLAUDE.md
- controlSkill
- filebaseSkill
- javascriptSkill
- jsexecSkill
- menusSkill
- mqttSkill
- smbutilsSkill
- textSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.