CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-jumpserver

Stateful CLI harness for JumpServer bastion host management. Supports asset, user, permission, account, session, audit, and operations management via REST API, with both one-shot and interactive REPL modes.

Quality

74%

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

Fix and improve this skill with Tessl

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

Quality

Content

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

A tight, example-first CLI reference that is genuinely executable for the common cases and well-sectioned. Its main weaknesses are the absent validation/verification pattern for destructive operations (delete, kill), an install path pointing outside the skill, and undocumented flags used in examples.

Suggestions

Add an explicit destructive-operation safety workflow, e.g. always run 'asset delete <ID> --dry-run --output json' first, confirm the preview, then execute and re-check with 'asset get <ID>'; do the same for 'session kill'. This also lifts the workflow_clarity cap of 3.

Fix or remove the 'cd agent-harness && pip install -e .' instruction — that directory is not part of the skill bundle — and document or drop the undocumented example flags ('--status failed', '--action delete', '--risk 5').

Consider moving the per-command-group detail and the four workflow recipes into one-level-deep reference files (e.g. workflows.md, commands/asset.md) to slim the single-file body of this broad CLI.

DimensionReasoningScore

Conciseness

The body is command-driven and table-based with almost no concept explanation ('All commands support `--output json`' followed immediately by an example), but it has minor trimmable padding: the intro sentence restates the frontmatter description, 'Monitor active sessions / session list --active --output json' is repeated verbatim in workflows 3 and 4, and the `cli-anything-jumpserver ... --output json` prefix is spelled out many times. This sits above anchor 3 (mostly efficient) but short of anchor 5 (every token earns its place).

4 / 5

Actionability

Nearly all guidance is copy-paste-ready command lines with concrete flags ('asset list --type host --output json', 'user create --name "New User" --username newuser --email user@example.com --output json --dry-run'), matching anchor 5's executable bar. It falls to 4 due to minor gaps: the install step 'cd agent-harness && pip install -e .' points at a directory that is not part of the skill bundle, and example flags like 'audit login --status failed', 'audit operate --action delete', and 'session command list --risk 5' are used without being documented anywhere in the body, so an agent cannot confirm they are valid.

4 / 5

Workflow Clarity

The four 'Typical Agent Workflows' present a clear sequence (e.g., check connection -> list -> get details; create with --dry-run -> verify via 'perm users <PERM_ID>'), and the body states 'All mutation commands support `--dry-run` to preview without execution'. However, the CLI covers destructive operations (asset/user delete, session kill) and no workflow shows an explicit validation checkpoint or error-recovery loop for them — deletes and kills appear only as bare subcommands with no verify step — so per the rubric cap for destructive/batch operations without validation, this cannot exceed anchor 3.

3 / 5

Progressive Disclosure

Sections are well-organized and appropriately scoped for an overview ('## Quick Start', '## Agent Usage Guidance', '## Output Formats', '## Exit Codes', '## File Locations'), with no nested or dead references, matching anchor 4's 'good structure; most content is appropriately placed'. It misses anchor 5 because no bundle files exist at all while the body still references an unbundled 'agent-harness' directory, and the per-group command detail plus the four workflow recipes are candidates for one-level-deep reference files given the CLI's breadth.

4 / 5

Total

15

/

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.

A well-scoped, product-specific description with strong distinctiveness and good keyword coverage. Its main gaps are the missing 'when to use' trigger clause and generic 'management' verbs instead of concrete actions.

Suggestions

Append a trigger clause, e.g. 'Use when managing JumpServer instances, bastion hosts, or when the user mentions JumpServer, PAM, or privileged access.'

Replace the generic 'management' nouns with concrete verbs for at least the top areas, e.g. 'create and list assets, manage users and asset permissions, view session recordings and audit logs'.

Add natural synonyms such as 'PAM', 'privileged access management', and 'bastion' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates several specific capability areas — 'asset, user, permission, account, session, audit, and operations management' — plus interaction modes ('one-shot and interactive REPL') and mechanism ('via REST API'), which exceeds anchor 3's '1-2 concrete actions' and matches anchor 4's 'several specific actions; minor gaps'. It falls short of anchor 5 because the actions are generic nouns ('management') rather than concrete verbs like create, list, update, or delete.

4 / 5

Completeness

The 'what' is explicit and detailed ('Stateful CLI harness for JumpServer bastion host management... via REST API, with both one-shot and interactive REPL modes'), but there is no 'Use when...' clause or any equivalent trigger guidance, so per the rubric cap completeness cannot exceed anchor 3 ('clear what; when missing or only weakly implied').

3 / 5

Trigger Term Quality

It contains the primary natural terms a user would say — 'JumpServer' and 'bastion host' — plus useful domain nouns (asset, user, permission, session, audit), matching anchor 4's 'good keyword coverage; a few natural terms missing'. It is below anchor 5 because common synonyms a user might naturally say, such as 'PAM', 'privileged access management', or 'SSH access', are absent.

4 / 5

Distinctiveness Conflict Risk

'JumpServer bastion host management' names a specific product and a specific operations niche, giving it clear distinct triggers and minimal conflict risk with any other skill category, which matches anchor 5 exactly; the only conceivable overlap would be another JumpServer-specific skill. It is clearly above anchor 4, which requires only 'minor overlap risk with closely related 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

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