CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-feature

Use when building or modifying pages, components, modules, routes, data loading, forms, API integration, or UI features — including small changes like a column, filter, or panel — in the orchestration cluster webapp (webapp/client/apps/orchestration-cluster-webapp/).

68

Quality

83%

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

78%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 dense, well-structured reference that assumes competence and provides concrete paths, commands, and Camunda-specific patterns, with details deferred to clearly listed canonical docs. The main improvement area is converting prose-described patterns into runnable code examples and tightening a few rationale sentences.

Suggestions

Add a short copy-paste code example for the preferred data-loading tier (queryOptions + ensureQueryData + useSuspenseQuery) so the top pattern is executable rather than described.

Trim rationale that restates widely-known concepts (e.g., the YAGNI and design-language justifications) to one phrase or remove, keeping only Camunda-specific why.

Turn the 'Building a feature' steps into an explicit ordered workflow with a validation checkpoint (run typecheck/lint) before declaring the feature done.

DimensionReasoningScore

Conciseness

Mostly lean and rule-driven with no padding about basic concepts, but a few rationale clauses (e.g., the YAGNI and design-language justifications) restate ideas Claude already knows and could be trimmed.

4 / 5

Actionability

Highly actionable with concrete commands (npm run prettier:format/lint/typecheck/test:unit), specific file paths (queries.ts, endpoints.ts, feature-flags.ts), and named APIs (useSuspenseInfiniteQuery, ensureQueryData), though patterns are often described in prose rather than full copy-paste code blocks.

4 / 5

Workflow Clarity

A clear implicit sequence (before-starting considerations -> pod/shared/route structure -> commit checks) with the local-checks section serving as a validation checkpoint, but no explicit validate-then-proceed feedback loop for error recovery.

4 / 5

Progressive Disclosure

Well-organized overview with clearly signaled one-level-deep references via the "Canonical docs" list pointing to eight monorepo docs, keeping the body an overview while deferring details appropriately.

5 / 5

Total

17

/

20

Passed

Description

87%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, well-scoped description that pairs an explicit "Use when" trigger with a concrete enumeration of feature work, tightly bound to one webapp. It is comprehensive on when/where and distinct, with only minor room to broaden action verbs and trigger synonyms.

DimensionReasoningScore

Specificity

Lists several specific feature types ("pages, components, modules, routes, data loading, forms, API integration, or UI features") with concrete small-change examples ("a column, filter, or panel"), but the verbs are limited to building/modifying, leaving a minor gap versus the most comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (building/modifying the enumerated feature types) and when ("Use when building or modifying... in the orchestration cluster webapp") with concrete trigger phrases, satisfying the top anchor.

5 / 5

Trigger Term Quality

Good coverage of natural frontend terms a developer would say (pages, components, routes, data loading, forms, API integration, filter, panel), though it lacks synonyms and file-extension-style triggers that would mark full comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named app with an explicit path ("orchestration cluster webapp (webapp/client/apps/orchestration-cluster-webapp/)"), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
camunda/camunda
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.