CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spl-to-apl

Translates Splunk SPL queries to Axiom APL. Provides command mappings, function equivalents, and syntax transformations. Use when migrating from Splunk, converting SPL queries, or learning APL equivalents of SPL patterns.

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

80%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.

The body is an exceptionally dense, executable translation reference — no padding, no background-concept explanations, and copy-paste APL for every common pattern including subqueries, joins, and transaction reconstruction. Its weaknesses are procedural: the translation workflow is implicit rather than sequenced, there is no verification step for the output, and all three referenced reference/*.md files are missing from the bundle, breaking progressive disclosure.

Suggestions

Add an explicit translation checklist (identify SPL commands → map each via the tables → add 'where _time between (ago(..) .. now())' → re-check the Critical Differences list) so the workflow is sequenced rather than implicit.

Include a final verification step, e.g. confirm every SPL command in the source query has a mapped APL equivalent and that the join-limit and cidrmatch arg-order gotchas were applied, before presenting the translation.

Ship the referenced bundle files — reference/command-mapping.md, reference/function-mapping.md, and reference/examples.md are all cited in the body but absent from the bundle.

DimensionReasoningScore

Conciseness

The body is almost entirely dense mapping tables, side-by-side SPL/APL examples, and gotchas ('Join is preview: limited to 50k rows', 'cidrmatch args reversed') with zero explanation of what Splunk or APL is. Matches the 5 anchor (lean, assumes Claude's competence, every token earns its place) rather than 4, which requires over-explanation to trim — none was found.

5 / 5

Actionability

Copy-paste-ready APL for the common cases — '| summarize errors = countif(status >= 500) by host', '| parse kind=regex message with @"user=(?P<username>\w+)"', "where _time between (ago(24h) .. now())" — plus complete SPL→APL command and function tables. Matches the 5 anchor (fully executable, specific examples cover the common cases).

5 / 5

Workflow Clarity

Well-organized for lookup (Critical Differences up front, per-command sections, dedicated time handling), but the translation procedure is implicit: no sequenced steps (decompose SPL → map commands → add explicit time range → re-check gotchas) and no verification step for the produced APL. Fits the 3 anchor (sequence present but checkpoints implicit/missing); not 4 because no explicit checklist or validation is present, and not lower since the destructive/batch validation cap does not apply to this read/translate skill.

3 / 5

Progressive Disclosure

References are clearly signaled and one level deep ('Complete mappings: reference/command-mapping.md', 'Complete function list: reference/function-mapping.md', 'reference/examples.md'), but none of the three referenced files exist in the bundle — no references/, scripts/, or assets/ directories are present, so navigation breaks at the second level. Fits the 3 anchor (structure present but incomplete); not 4 because broken reference paths are more than a minor organization gap.

3 / 5

Total

16

/

20

Passed

Description

100%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.

The description is a model example: it states a precise what (translate SPL to APL via command mappings, function equivalents, and syntax transformations) and an explicit when (migrating from Splunk, converting SPL queries, learning APL equivalents), in third person with no padding or buzzwords. Trigger coverage includes both product names, both query-language names, and the natural intent verbs.

DimensionReasoningScore

Specificity

'Translates Splunk SPL queries to Axiom APL. Provides command mappings, function equivalents, and syntax transformations' names the exact domain and multiple concrete deliverables with no generic language. Matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, which expects minor gaps — the command, function, and syntax layers are all enumerated.

5 / 5

Completeness

Explicit 'what' ('Translates Splunk SPL queries to Axiom APL. Provides command mappings, function equivalents, and syntax transformations') followed by an explicit trigger clause ('Use when migrating from Splunk, converting SPL queries, or learning APL equivalents of SPL patterns'). Exactly the 5 anchor structure; not 4 because the 'when' is fully explicit rather than needing more specificity.

5 / 5

Trigger Term Quality

All natural terms a user would say are present: 'Splunk', 'SPL', 'Axiom', 'APL', 'migrating from Splunk', 'converting SPL queries', 'learning APL equivalents' — covering both product names, both query languages, and three intent verbs. Matches the 5 anchor's comprehensive synonym coverage; not 4 since no commonly used trigger variation is missing.

5 / 5

Distinctiveness Conflict Risk

'Splunk SPL queries to Axiom APL' is a clear niche with domain-specific triggers (Splunk, SPL, Axiom, APL) and no generic phrasing that would fire for unrelated skills. Matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk).

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openclaw/clawhub

Path

.agents/skills/spl-to-apl/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.