CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keda

Design, debug, and review KEDA ScaledObject/ScaledJob autoscaling. Covers all major scalers (Prometheus, SQS, Kafka, Redis, Cron, HTTP Add-on, Azure Service Bus), TriggerAuthentication, scaling lifecycle tuning, GitOps integration, and troubleshooting. Use when asked to "add KEDA autoscaling", "debug why my ScaledObject isn't scaling", "review my KEDA config", or "generate a ScaledObject for <trigger>".

Quality

92%

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

The canonical home for this skill is keda in nitinjain999/platform-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, well-structured, and highly actionable: exact kubectl commands, precise field names, condition-to-cause mappings, and explicit validation/verification steps across all four modes. Its two real weaknesses are that the only referenced bundle file (references/keda.md) does not exist — stranding the sizing table, decision matrix, and deeper troubleshooting content the body defers to it — and that the generate mode lacks a single complete worked example.

Suggestions

progressive_disclosure: Ship the missing references/keda.md (or remove the deferrals) — the body points to it three times for the pollingInterval/cooldownPeriod sizing table, the KEDA-vs-HPA decision matrix, and deeper troubleshooting, but the bundle has no references/ directory, so that content is unreachable.

actionability: Include one complete worked example in the generate mode (a full ScaledObject + TriggerAuthentication with IRSA auth for a common scaler like SQS or Kafka) so generated specs don't rely on model priors for structure and trigger metadata fields.

progressive_disclosure: Add minimal inline fallback guidance (e.g., a one-line rule of thumb for sizing pollingInterval/cooldownPeriod per workload pattern) so the generate and scale modes remain usable even when the reference file is unavailable.

DimensionReasoningScore

Conciseness

The body never explains basics Claude already knows — no 'KEDA is a...' boilerplate, no YAML/Kubernetes tutorials — and every section is terse directive content: exact commands ("kubectl logs -n keda -l app.kubernetes.io/name=keda-operator --tail=100"), field checklists ("activationThreshold/activationQueueLength set to avoid flapping"), and operational warnings ("Scale-to-zero warning"). Matches the 5 anchor — every token earns its place; not 4 because there is no padded or over-explained passage to trim beyond the single conventional one-line scope opener.

5 / 5

Actionability

Concrete, executable guidance throughout: exact kubectl collect commands, the HPA naming convention ("keda-hpa-<scaledobject-name>"), exact field names ("advanced.restoreToOriginalReplicaCount: true", "scaleDown.stabilizationWindowSeconds"), and a copy-paste verify command ("kubectl get deployment <name> -n <namespace> -o jsonpath='{.spec.replicas}'"). Falls short of 5 because the generate mode is a field checklist with no complete worked ScaledObject/TriggerAuthentication example, and trigger-specific metadata specifics are deferred to a reference file that is not in the bundle; better than 3 because what is written is directly executable, not pseudocode.

4 / 5

Workflow Clarity

All four modes are clearly sequenced with explicit validation checkpoints: debug is collect → condition interpretation ("Active: false → scaler is not detecting events (check trigger config and auth)") → ordered checklist → root cause → "the command to verify it" (a full feedback loop); generate ends with a validation command and the expected "Active: true" condition; rollback includes verify-and-remediate steps. Matches the 5 anchor (clear sequence, explicit validation, feedback loops, checklists); not 4 because checkpoints and error-recovery steps are explicit in every mode that needs them.

5 / 5

Progressive Disclosure

Body structure is good and the references are clearly signaled and one level deep ("If you need deeper context on KEDA troubleshooting, scaling lifecycle, or scaler-specific behaviour, load `references/keda.md`"), but the bundle contains no references/, scripts/, or assets/ directories — the sole referenced file does not exist, so the deferred pollingInterval/cooldownPeriod sizing table and the KEDA-vs-HPA decision matrix are unreachable. The broken deferral is a larger problem than anchor 4's 'minor organization gaps', though the body itself avoids anchor 2's inlining problem — between the two, landing at 3.

3 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: three concrete actions (design, debug, review) on named resource kinds, comprehensive coverage of scalers, auth, lifecycle tuning, and GitOps, and an explicit 'Use when' clause with four natural quoted trigger phrases keyed to the distinctive 'KEDA' term. Written in third-person imperative voice with no vague padding or over-claims.

DimensionReasoningScore

Specificity

"Design, debug, and review KEDA ScaledObject/ScaledJob autoscaling" names multiple concrete actions on specific resource kinds, and "Covers all major scalers (Prometheus, SQS, Kafka, Redis, Cron, HTTP Add-on, Azure Service Bus), TriggerAuthentication, scaling lifecycle tuning, GitOps integration" gives comprehensive coverage within the domain. Matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); not 4 because no meaningful capability within the KEDA domain is left uncovered.

5 / 5

Completeness

"Design, debug, and review KEDA ScaledObject/ScaledJob autoscaling" explicitly answers what, and "Use when asked to 'add KEDA autoscaling', 'debug why my ScaledObject isn't scaling'..." explicitly answers when with concrete trigger phrases. This is a direct match to the 5 anchor (both what and when with concrete trigger phrases); not 4 because the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

The quoted triggers "add KEDA autoscaling", "debug why my ScaledObject isn't scaling", "review my KEDA config", and "generate a ScaledObject for <trigger>" are phrasings users would naturally say, anchored on the distinctive term "KEDA" plus resource names (ScaledObject, KEDA config). Matches the 5 anchor's comprehensive natural-term coverage; not 4 because both the primary tool name and multiple natural phrasing variants (add/debug/review/generate) are present.

5 / 5

Distinctiveness Conflict Risk

Terms like "KEDA", "ScaledObject/ScaledJob", "TriggerAuthentication", and "debug why my ScaledObject isn't scaling" occupy a clear niche with virtually no overlap with adjacent skills (generic Kubernetes/HPA help would not use these terms). Matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk); not 4 because the triggers are keyed to proper nouns only this skill handles.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

nitinjain999/platform-skills

Path

plugins/platform-skills/skills/keda/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.