agentleFS
StosanStosan/Claude-Skills-for-engineering-teams/skills/application-log-reader/SKILL.md

application-log-reader

Skill2 starsChanged 4 days agoNo licenceView on GitHub

Use this skill whenever a user needs to analyze, parse, trace, or debug application logs from any environment. Trigger when users say things like “read my logs,” “analyze these logs,” “find the error,” “debug this output,” “my app is crashing,” “something failed in production,” “trace this stack trace,” or “help me find the root cause.” Also activate when users paste raw logs, stack traces, crash reports, runtime output, or upload log files from GCP Cloud Run, Docker, Kubernetes, VMs, local machines, or other runtimes. If logs are shared alongside a codebase, use both together. This skill performs deep forensic debugging — not surface scanning. It correlates logs with source code to pinpoint the exact failure origin down to the file, module, function, and execution path, then prescribes precise fixes, likely causes, and remediation steps.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.