CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tal

Write, compile, inspect and verify Trace Analysis Language (TAL) rules for the OTLP and SkyWalking native (sw-native) inputs — rule files, the compiler and runtime map, dumping and decompiling the generated classes, the v1-v2 checker, the branch gate and the benchmark. Use when changing TAL rules, the TAL grammar/compiler, or the native trace analysis.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally dense, high-signal body: all guidance is executable with exact commands, paths, and class names, and nothing explains concepts Claude already knows. The two minor gaps are the absence of an explicit error-recovery loop in the verify workflow and the lack of any bundle split for the longer reference-style recipes.

Suggestions

Add an explicit feedback loop to the Verify workflow, e.g. "If the v1-v2 checker or branch gate fails, fix the rule (or add the branch to checker-allowed-misses.yml only if the miss is expected), then re-run both test commands before proceeding."

Move the IntelliJ/FernFlower decompile recipe and the function-registry inventory into a references/ file (e.g. references/decompile.md, references/runtime-map.md), keeping SKILL.md to the dump command and one-line pointers.

DimensionReasoningScore

Conciseness

Nearly every line carries project-specific, non-inferable facts — the generated class-name scheme "{file}_L{line}_{rule}", the native file-order contract, Javassist constraints ("no imports", "no autoboxing"), and the measured per-run allocation rules. It assumes Claude's competence (no explanation of what decompilers, JMH, or JaCoCo are), so every token earns its place per the score-5 anchor.

5 / 5

Actionability

Guidance is copy-paste ready: complete ./mvnw commands for dumping, installing, testing, and benchmarking; a full FernFlower ConsoleDecompiler invocation; exact config keys (SW_TRACE_NATIVE_TAL_FILES, checker-allowed-misses.yml) and file paths. Specific commands cover the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

The Verify section has a clear sequence with explicit preconditions ("Once, and after any cross-module change: … install the backend reactor first") and real validation (the v1-v2 checker, the branch gate, reading checker-events files), and the branch-gate paragraph explains failure handling. It falls short of the score-5 anchor because there is no explicit fix-and-re-run feedback loop (e.g., what to do when a checker comparison fails) and the skill is structured as parallel sub-workflows rather than one fully checkpointed sequence.

4 / 5

Progressive Disclosure

Good structure: clear section headers per task area, comparison tables, and well-labeled code blocks, with repo doc paths clearly listed for sync. It is not the score-5 case (a lean overview with well-signaled one-level references): the file is ~106 lines with no bundle split, and self-contained recipes such as the IntelliJ/FernFlower decompile setup and the function-registry inventory could live in reference files.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, verb-led, and comprehensive over the skill's task areas, with an explicit and specific "Use when" trigger clause and an unambiguous niche. The only weakness is a handful of missing natural synonyms (trace-analyzer, agent-analyzer, .tal files) that slightly narrow trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates concrete actions across the full lifecycle — "Write, compile, inspect and verify" plus "dumping and decompiling the generated classes, the v1-v2 checker, the branch gate and the benchmark" — giving comprehensive, not just partial, coverage. It exceeds the score-4 anchor ("several specific actions; minor gaps") because every major task area of the skill is named.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the leading verb list with named artifacts, and the "when" is a concrete trigger clause — "Use when changing TAL rules, the TAL grammar/compiler, or the native trace analysis". This matches the score-5 anchor (clear what AND when with concrete trigger phrases), not score 4 where the "when" would be less specific.

5 / 5

Trigger Term Quality

Good natural-term coverage: "TAL rules", "OTLP", "SkyWalking native (sw-native)", "TAL grammar/compiler", "native trace analysis", including the sw-native synonym. A few natural terms a user might say are missing, such as "trace-analyzer", "agent-analyzer", or ".tal"/"talFiles", so it fits the score-4 anchor rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Trace Analysis Language (TAL) rules for the OTLP and SkyWalking native (sw-native) inputs" stakes out a clear niche with distinct triggers; no other plausible skill overlaps with TAL rule compilation or the SkyWalking native trace path. Minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

apache/skywalking

Path

.claude/skills/tal/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.