CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-nslogger

CLI harness for NSLogger — parse, filter, export, and monitor NSLogger log files (.rawnsloggerdata / .nsloggerdata)

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./nslogger/agent-harness/cli_anything/nslogger/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a lean, fully executable command reference with concrete examples for every subcommand, documented JSON output shapes, and a clear numbered agent workflow. It stays appropriately concise with only minor repetition between the command reference and workflow examples, and its flat, well-labeled structure makes it easy to navigate without any bundle files.

DimensionReasoningScore

Conciseness

The body is almost entirely executable commands with terse comments and no background explanations, but the Agent Workflow Examples section repeats commands already shown and the listen section enumerates six variants, leaving minor instances that could be trimmed.

4 / 5

Actionability

Every section provides copy-paste-ready cli-anything-nslogger invocations covering all subcommands and common flag combinations, and the JSON output shapes for stats and messages are documented so agents can parse results directly.

5 / 5

Workflow Clarity

The numbered 5-step crash-analysis sequence is clear and cumulative, and the operations are read-only so the destructive/batch validation cap does not apply; however, there are no explicit checkpoints or error-recovery guidance (e.g., what to do if a listen connection never arrives), matching 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Sections are well-organized per subcommand with no nested references (and no bundle files exist), keeping navigation easy; the ~20-line Message JSON Shape and per-flag example blocks could arguably move to a reference file, which keeps this at 'good structure; minor organization gaps' rather than the well-split anchor 5.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific, niche, and includes the tool name and file extensions, making it highly distinguishable. Its main weakness is the absence of any "when to use" guidance, which limits discoverability and caps completeness. Adding an explicit trigger clause would substantially improve it.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when working with NSLogger log captures (.rawnsloggerdata / .nsloggerdata), live NSLogger monitoring, or iOS/macOS log debugging.'

Include a few natural trigger synonyms users would say, such as 'iOS/macOS logs', 'log viewer', or 'log debugging', to improve trigger term coverage.

Mention the stats/generate capabilities (e.g. 'summarize log statistics') to close the minor coverage gap in the capability list.

DimensionReasoningScore

Specificity

"parse, filter, export, and monitor" lists four concrete actions with the tool domain and file extensions, but omits capabilities present in the body (stats, generate, repl), matching 'several specific actions; minor gaps in coverage' rather than the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clear (a CLI harness that parses, filters, exports, and monitors NSLogger log files), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"NSLogger", "log files", and ".rawnsloggerdata / .nsloggerdata" give good keyword coverage including file extensions, but natural phrasings users might say such as "iOS/macOS logs", "log viewer", or "debugging logs" are missing.

4 / 5

Distinctiveness Conflict Risk

The description is tied to a specific named tool and its proprietary file extensions (.rawnsloggerdata / .nsloggerdata), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

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

HKUDS/CLI-Anything

Path

nslogger/agent-harness/cli_anything/nslogger/skills/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.