integrate

Add Olakai monitoring to existing AI code — wrap your LLM client, configure custom KPIs, and validate the integration end-to-end

Quality

61%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./content/olakai/skills/integrate/SKILL.md

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 is highly actionable with excellent executable code examples and a well-structured validation workflow with error recovery paths. However, it is severely bloated — it tries to be a comprehensive reference document rather than a concise skill, explaining motivations and concepts Claude doesn't need, duplicating patterns across languages, and inlining content that should be in separate reference files. Cutting this to ~30-40% of its current size while splitting framework examples and formula references into separate files would dramatically improve it.

Suggestions

Remove the 'Why Custom KPIs Are Essential' section entirely — Claude doesn't need motivation, just instructions on what to do.

Move framework-specific integrations (Next.js, FastAPI), edge cases (streaming, error handling, non-OpenAI providers), and KPI formula reference into separate referenced files to reduce the main skill to a focused overview.

Consolidate TypeScript and Python examples — show one language inline and reference the other, or use a compact side-by-side format instead of duplicating every example.

Remove explanatory prose like 'Adding monitoring is only the first step' and 'The real value of Olakai comes from...' — replace with terse directives.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines. It explains concepts Claude already knows (what KPIs are, why monitoring matters, what streaming is), includes a 'Why Custom KPIs Are Essential' motivational section, repeats the same patterns in both TypeScript and Python redundantly, and provides framework-specific examples (Next.js, FastAPI) that inflate token count significantly. The 'Understanding the customData to KPI Pipeline' section explains basic data flow concepts unnecessarily.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready code examples in both TypeScript and Python. CLI commands are specific and complete with flags. The before/after code comparison pattern is effective, and the customData-to-KPI pipeline includes concrete bash commands for every step.	3 / 3
Workflow Clarity	The multi-step integration process is clearly sequenced (Steps 1-5) with explicit validation checkpoints. The 'Test-Validate-Iterate Cycle' section includes a detailed validation flow diagram with specific error recovery paths (check API key, fix field name case, create CustomDataConfig). The feedback loop for KPI validation is thorough with correct/wrong examples.	3 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to supporting files. The content includes framework-specific integrations, edge cases, KPI formula references, and quick references all inline. The only external reference is a URL to full SDK docs. Content like the formula reference, framework examples, and edge cases should be split into separate files.	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 naming the Olakai product and listing concrete integration steps. However, it lacks an explicit 'Use when...' clause which hurts completeness, and uses second person voice ('your') instead of third person. Trigger term coverage could be broader to capture alternative phrasings users might employ.

Suggestions

Add a 'Use when...' clause such as 'Use when the user wants to add Olakai monitoring, observability, or tracing to their AI/LLM application.'

Switch from second person ('wrap your LLM client') to third person ('wraps the LLM client, configures custom KPIs, and validates the integration end-to-end').

Include additional trigger terms like 'observability', 'tracing', 'LLM logging', or 'AI analytics' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'wrap your LLM client', 'configure custom KPIs', and 'validate the integration end-to-end'. These are clear, actionable steps.	3 / 3
Completeness	Clearly answers 'what' (add Olakai monitoring by wrapping LLM client, configuring KPIs, validating integration), 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 relevant terms like 'Olakai', 'monitoring', 'LLM client', 'KPIs', and 'integration', but misses common variations users might say such as 'observability', 'tracing', 'logging', 'AI monitoring', or 'LLM analytics'. Also uses second person ('your') which is noted but scored under specificity per rubric.	2 / 3
Distinctiveness Conflict Risk	Very specific to Olakai as a product and its monitoring integration workflow. The brand name 'Olakai' combined with specific actions like wrapping LLM clients makes this highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

72%

Warnings & errors only

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

Validation — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (661 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
Commit: 67dcbeb

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

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.