ark-sdk-development
Regenerate and debug types across the ARK stack (SDK, API, Dashboard). Use when fixing TypeScript type errors in ark-dashboard, updating types after CRD changes, regenerating types.ts from OpenAPI spec, debugging "Property does not exist on type" schema errors, or adding custom SDK functionality via overlays. Covers the full type pipeline from Kubernetes CRDs to TypeScript.
97
96%
Does it follow best practices?
Impact
100%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger terms (including an exact error message), has an explicit 'Use when...' clause with multiple scenarios, and is highly distinctive due to its project-specific terminology. The description is concise yet comprehensive, covering the full scope without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: regenerate types, debug types, fix TypeScript type errors, update types after CRD changes, regenerate types.ts from OpenAPI spec, debug schema errors, add custom SDK functionality via overlays. Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (regenerate and debug types across the ARK stack) and 'when' with an explicit 'Use when...' clause listing five specific trigger scenarios. Also provides scope context with 'Covers the full type pipeline from Kubernetes CRDs to TypeScript.' | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'TypeScript type errors', 'ark-dashboard', 'CRD changes', 'types.ts', 'OpenAPI spec', 'Property does not exist on type', 'SDK', 'overlays'. Includes the exact error message a user might paste, which is particularly effective. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: ARK stack type pipeline from Kubernetes CRDs to TypeScript. The specific project names (ark-dashboard, ARK SDK/API), technologies (OpenAPI spec, CRDs), and error patterns make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently documents a complex multi-service type generation pipeline. Its greatest strengths are the clear pipeline visualization, the critical Pydantic naming convention with concrete examples and safety net, and the actionable debugging workflow. The content is appropriately concise while covering all necessary details for the ARK type development workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude understands Kubernetes CRDs, Pydantic, OpenAPI, and TypeScript without explaining any of these concepts. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete, executable commands (make targets, npm commands, bash commands), specific file paths, a clear naming convention table with examples, and exact grep commands for debugging. The Pydantic naming section is particularly actionable with its domain-prefix pattern and concrete examples. | 3 / 3 |
Workflow Clarity | The type generation pipeline is clearly visualized with an ASCII flow diagram showing the full chain from CRD YAML to TypeScript types. Multi-step processes include numbered steps, and the debugging section provides a clear sequence with validation (npm run build to verify). The safety net in generate_openapi.py serves as an explicit validation checkpoint for the critical naming collision issue. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a key files reference table, but it's all inline in a single file. For a skill of this complexity covering three different services (SDK, API, Dashboard), some content like the Pydantic naming conventions or debugging procedures could be split into referenced files. However, the length is manageable and the organization is logical. | 2 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mckinsey/agents-at-scale-ark
- Commit
f4bfd2d
- 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.