CtrlK
BlogDocsLog inGet started
Tessl Logo

cekura-fixing-prod-issues

Debugs a failing production call, reproduces the bug with Cekura evaluators, implements a fix, verifies it, runs regression tests, then raises a PR with evidence. Use when the user wants to fix a production call bug, investigate a failing prod call, reproduce and fix a production issue, run regression tests before a PR, or says things like "fix this prod call issue", "debug and fix call ID", "test my fix against prod scenarios", "reproduce this production bug", or "regression test before raising PR".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced orchestrator with excellent workflow gating, but it is held back by some explanatory padding and by referencing six phase files that do not exist in the bundle, which undermines both actionability and progressive disclosure.

Suggestions

Provide the referenced phase1-debug.md through phase6-pr.md files (or inline their key steps) so the signaled navigation resolves to real content.

Trim inferential rationale from the Strictness Rules (e.g. the 'The sequence exists because' bullets) to keep the body lean.

Add at least one concrete, executable snippet per phase (command or API call) in the body so the overview is actionable even before the phase files are opened.

DimensionReasoningScore

Conciseness

Mostly efficient, but the strictness rules pad with rationale Claude could infer — 'The sequence exists because: You cannot write a good fix without understanding the root cause' and 'The bug lives in the real call path; only a simulation over the same medium can confirm it' — so it lands at 'mostly efficient but could be tightened' rather than the lean top anchor.

2 / 3

Actionability

Gives concrete gates and one real endpoint ('GET /test_framework/v1/ai-agents/{id}/'), but the executable detail for each phase is delegated to phase1-debug.md…phase6-pr.md, which are not present in the bundle, leaving the guidance incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

The 6 phases are clearly sequenced with explicit validation checkpoints and feedback loops — 'eval must fail before any fix', 'eval must pass now', 'Never push code until Phase 5 is complete' — matching the anchor for a clear sequence with explicit validation and error-recovery gating.

3 / 3

Progressive Disclosure

The overview is well-structured and references are one level deep and clearly signaled in a table, but every linked file (phase1-debug.md through phase6-pr.md) is missing from the bundle, so the signaled navigation leads nowhere and the disclosure is broken in practice.

2 / 3

Total

9

/

12

Passed

Description

100%

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, third-person description that states concrete actions, gives explicit 'Use when' triggers with natural user phrasings, and occupies a distinct niche. It satisfies all four dimensions at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in sequence — 'Debugs a failing production call, reproduces the bug with Cekura evaluators, implements a fix, verifies it, runs regression tests, then raises a PR with evidence' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' (the debug→reproduce→fix→verify→regression→PR chain) and 'when' via an explicit 'Use when the user wants to...' clause with multiple triggers, matching the anchor for clearly answering both.

3 / 3

Trigger Term Quality

Quotes natural user phrasings verbatim — 'fix this prod call issue', 'debug and fix call ID', 'test my fix against prod scenarios', 'reproduce this production bug', 'regression test before raising PR' — giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Cekura production-call bug fixing with a defined 6-phase workflow) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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

relative_links

Relative link issues: 6 missing

Warning

Total

15

/

16

Passed

Repository
cekura-ai/cekura-skills
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.