CtrlK
BlogDocsLog inGet started
Tessl Logo

new-project

Build a new AI agent with Olakai monitoring from scratch — project setup, SDK integration, KPI configuration, and end-to-end validation

52

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./content/olakai/skills/new-project/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%

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

The skill excels at actionability with complete, executable code examples and workflow clarity with explicit validation checkpoints and error recovery paths. However, it is severely undermined by its length and monolithic structure — it tries to be both a quick-start guide and a comprehensive reference in one file, resulting in a document that is far too verbose and poorly organized for efficient context window usage. Splitting reference tables, SDK examples, and formula patterns into separate files would dramatically improve both conciseness and progressive disclosure.

Suggestions

Extract the KPI Formula Reference, Task Categories Reference, and Built-in Context Variables tables into separate reference files (e.g., FORMULAS.md, REFERENCE.md) and link to them from the main skill

Remove the 'Why Custom KPIs Are Essential' section and the 'What you can measure with KPIs' bullets — Claude doesn't need to be convinced of KPI value, it needs to know how to implement them

Consolidate SDK examples: keep one language (TypeScript) inline as the primary example and move Python and REST API implementations to a separate EXAMPLES.md file

Remove the 'What NOT to Include in customData' table and replace with a single sentence: 'Don't duplicate auto-tracked fields (session ID, tokens, model, timestamps, user email) in customData'

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~450+ lines. It explains concepts Claude already knows (what KPIs are, what agentic vs assistive AI means, what business questions are), includes extensive tables of built-in variables and task categories that could be in reference files, and repeats the same patterns across TypeScript/Python/REST implementations. The 'Why Custom KPIs Are Essential' section and 'What you can measure with KPIs' bullets are unnecessary padding.

1 / 3

Actionability

The skill provides fully executable CLI commands, complete TypeScript and Python code examples with imports and error handling, curl commands for REST API, and specific jq commands for validation. All code is copy-paste ready with realistic parameter names and proper structure.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with explicit dependencies (e.g., 'This step MUST be completed before Step 3'). Step 4 includes a detailed validation flow diagram with specific fix actions for each failure mode (customData missing → fix SDK, kpiData not numeric → fix formula, kpiData null → create CustomDataConfig). The production checklist adds a final verification gate.

3 / 3

Progressive Disclosure

This is a monolithic wall of text with no bundle files or external references. The KPI formula reference, task categories reference, built-in context variables table, and full SDK implementations in three languages should be split into separate reference files. Everything is inlined into a single massive document with no progressive disclosure structure.

1 / 3

Total

8

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong in specificity and distinctiveness, clearly listing concrete actions and targeting a well-defined niche around Olakai-monitored AI agent creation. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill, and could benefit from additional natural trigger terms users might employ.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to create a new AI agent project with Olakai observability, or asks about setting up monitoring for an agent from scratch.'

Include additional natural trigger terms such as 'observability', 'new agent project', 'scaffold', 'monitoring setup', or 'instrument an agent' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: project setup, SDK integration, KPI configuration, and end-to-end validation. These are distinct, actionable steps in a clear workflow.

3 / 3

Completeness

Clearly answers 'what' (build a new AI agent with Olakai monitoring, covering setup through validation), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes some relevant terms like 'AI agent', 'SDK integration', 'KPI configuration', and 'Olakai monitoring', but misses common user variations (e.g., 'observability', 'tracking', 'new project', 'scaffold'). 'Olakai' is a specific product name which helps, but natural user phrasing could vary.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Olakai monitoring' with 'AI agent' creation from scratch is a very specific niche. The mention of a specific product (Olakai) and the full lifecycle (setup to validation) makes it unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

72%

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

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

8

/

11

Passed

Repository
andrewyng/context-hub
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.