CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cmdk-actions

Guide for adding new actions to Sentry's Command+K palette. Use when implementing new cmdk actions, registering page-level or global actions, building async resource pickers, or adding contextual actions to a view.

67

Quality

84%

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

71%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 high-quality, dense reference with mostly executable code examples and a useful closing checklist, hindered mainly by its monolithic single-file structure and some duplication between inline rules and the checklist. Splitting advanced patterns into reference files would improve both token efficiency and progressive disclosure.

Suggestions

Split advanced material (patterns 7-9, the workflow state machine, and capability config sections) into a references/ file, keeping SKILL.md to slots, props, and the common patterns to cut always-loaded context.

Deduplicate rules restated verbatim in the checklist (staleTime, enabled, key naming) — reference the rule's section instead of repeating it, or trim the inline statement.

Complete the elided code snippets (the DSN lookup's apiOptions call and 'resource={helpResource}') so every pattern is copy-paste executable, and fix the duplicated '### 7.' section numbering.

DimensionReasoningScore

Conciseness

Prose is terse and directive, focused on repo-specific knowledge Claude doesn't have (slot lifetimes, drill-in query clearing, auto-render limitations) with no padding about known concepts. Not 5: several rules (staleTime, enabled, key naming) are stated inline and then restated in the checklist, and the assignee avatar example repeats across patterns 3 and 6.

4 / 5

Actionability

The core patterns (navigation, callback, static group, async resource picker, render-prop) are complete with imports, real file paths, and API endpoints — near copy-paste ready. Not 5: a few supplementary snippets are elided placeholders ('apiOptions.as<DsnLookupResponse>()(/* ... */)', 'resource={helpResource}', '<ProjectAvatar ... />').

4 / 5

Workflow Clarity

Logical progression from slots decision table to props to patterns to registration and gating, capped by an explicit verification checklist. Not 5: the implementation sequence (choose slot → choose pattern → implement → verify against checklist) is implied by structure rather than explicitly sequenced, and there are no error-recovery feedback loops.

4 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, tables, and a checklist, so navigation is decent. Not 4/5: everything (~690 lines) is inlined in a single monolithic SKILL.md with no reference files; the pattern catalog, workflow state machine, and capability-config sections are candidates for separate reference files to reduce always-loaded tokens.

3 / 5

Total

15

/

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: third-person, concise, and specific, with an explicit 'Use when' trigger clause covering the skill's main use cases. The only minor gap is a few natural trigger phrasings (e.g., 'command palette' standalone) not literally present.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'registering page-level or global actions, building async resource pickers, or adding contextual actions to a view' — which comprehensively mirror the patterns the skill body covers. Not 4: there are no coverage gaps; the enumerated capabilities span the skill's full scope.

5 / 5

Completeness

It clearly answers 'what' ('Guide for adding new actions to Sentry's Command+K palette') and 'when' with an explicit 'Use when implementing new cmdk actions...' clause listing four concrete triggers. Not 4: the when-guidance is fully explicit, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Good keyword coverage including both the abbreviation ('cmdk actions') and the full name ("Sentry's Command+K palette"), plus action-type phrases users would naturally say. Not 5: a few natural phrasings such as 'command palette' as a standalone term or 'search actions' are not literally present.

4 / 5

Distinctiveness Conflict Risk

"Sentry's Command+K palette" and 'cmdk' carve out a clear niche with distinct triggers tied to a specific codebase; minimal conflict risk with other skills.

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

skill_md_line_count

SKILL.md is long (693 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

getsentry/sentry

Path

.agents/skills/cmdk-actions/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.