log-pattern-triager
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: log-pattern-triager
description: Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause bu…
category: data
runtime: no special runtime
---
# log-pattern-triager output preview
## PART A: Task fit
- Use case: Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause buckets. Use when logs are noisy and need fast pattern extraction. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause buckets. Use when logs are noisy and need fast pattern extraction. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: log-pattern-triager
description: Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause bu…
category: data
source: 00PrabalK00/claude-skills
---
# log-pattern-triager
## When to use
- Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause buckets. Use when logs a…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "log-pattern-triager" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Log Pattern Triager
Overview
Cluster large log sets into likely issue groups, repeated signatures, and probable root-cause buckets.
Core Workflow
- Gather the full input corpus and normalize messy, repetitive, or partial artifacts into a usable working set.
- Cluster related items into themes, categories, or issue groups without flattening important differences.
- Extract the strongest signals, representative examples, and unresolved questions from each cluster.
- Produce a structured summary that is actionable for the next human or agent in the workflow.
Deliver
- A clear thematic summary or grouped output with representative evidence.
- The most important patterns, edge cases, and unknowns in the corpus.
- Actionable next steps, owners, or decisions when the task calls for them.
Guardrails
- Do not over-merge distinct issues just to simplify the summary.
- Preserve nuance when a cluster contains disagreement or uncertainty.
- Make the grouping logic legible enough that someone can audit it later.
- Prefer repository evidence, command output, and nearby tests over vague intuition.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review