CtrlK
BlogDocsLog inGet started
Tessl Logo

yandex-tracker-cli

CLI for Yandex Tracker (bash + curl). Queues, issues, comments, worklogs, attachments, YQL.

72

1.66x
Quality

73%

Does it follow best practices?

Impact

80%

1.66x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bkamuz--yandex-tracker-cli/skills/yandex-tracker-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable with executable commands and good structure, but workflow clarity is held back by missing validation feedback loops around destructive operations, and there is minor redundancy in the transition explanations.

Suggestions

Add explicit validation/verification steps for destructive commands (e.g. confirm before `issue-delete`, verify a transition succeeded after `issue-transition close`) to lift workflow clarity past the cap.

De-duplicate the transition documentation that currently appears in the command table, the examples block, and the Примечания section.

Consider moving the large examples block or the project-by-partial-name workflow into a separate reference file to improve progressive disclosure given the file exceeds 50 lines.

DimensionReasoningScore

Conciseness

The body is mostly efficient — a command reference table and copy-paste examples that assume Claude knows curl/jq — with only minor redundancy (transitions re-explained in table, examples, and notes) that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready bash commands and a complete command table covering common cases (e.g. `echo '{...}' | yandex-tracker issue-create BIMLAB "Новая задача"`).

5 / 5

Workflow Clarity

Sequences exist (installation steps, the 6-step project-by-partial-name workflow with conditional checkpoints), but destructive operations like `issue-delete` and `issue-close` lack explicit validation/verification feedback loops, which caps this dimension at 3.

3 / 5

Progressive Disclosure

Well-organized into clear sections (Установка, Использование, Примечания, Security, Структура, Limitations) in a self-contained file with no nested references; not a 5 only because it exceeds 50 lines without splitting any content into separate files.

4 / 5

Total

16

/

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 and distinctive, naming a clear product niche and several capability areas, but it lacks an explicit "when to use" trigger clause, which caps its completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when managing Yandex Tracker issues, queues, comments, worklogs, or attachments from the command line."

Convert the capability nouns into concrete actions (e.g. "create and update issues, add comments and worklogs, upload/download attachments, search via YQL") to strengthen specificity.

Include common synonyms or file/identifier forms (e.g. issue IDs like BIMLAB-123) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "Queues, issues, comments, worklogs, attachments, YQL" — beyond just naming the domain, though they are nouns rather than verb-form actions, leaving minor gaps.

4 / 5

Completeness

The "what" is clear ("CLI for Yandex Tracker (bash + curl)...") but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural domain terms a user would say ("Yandex Tracker", "issues", "comments", "worklogs", "YQL") are present with good coverage; a few synonyms/variations are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

"Yandex Tracker" is a specific product niche with distinct triggers, and the bash+curl framing makes conflict with other skills minimal.

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.

Validation15 / 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
dvcrn/openclaw-skills-marketplace
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.