CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tools

Give your agents capabilities through tools (function calling). Helps you identify what your agent needs to do, create tool definitions, and attach them to config variations.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/tools/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a strong, highly actionable skill body: concrete tool invocations, executable code, an explicitly sequenced workflow with verification and error-recovery guidance, and appropriate externalization of per-provider detail. The only weaknesses are minor repetition and an inline provider-conversion section that sits at the boundary of what should be a reference file.

DimensionReasoningScore

Conciseness

The body is dense and almost every token carries LaunchDarkly-specific or provider-specific information Claude cannot safely assume, but there is minor duplication: the anti-clobber warning appears in both Step 3 and "What NOT to Do", and the four-step ordering is stated twice in Step 1 and Core Principles.

4 / 5

Actionability

Exact MCP tool names ("create-ai-tool", "update-agent-config" with resource: "variation"), complete JSON payloads, copy-paste-ready Python conversion snippets for four providers, and concrete per-provider stop-reason signals (e.g. "response.stop_reason != 'tool_use'") fully cover the common cases.

5 / 5

Workflow Clarity

The four-step workflow is explicitly sequenced with a dedicated verify step ("Use get-agent-configs to confirm the tool is attached"), an edge-case table with recovery actions (409 → "Use existing or create with different key"), and explicit guardrails against silently clobbering UI-edited fields.

5 / 5

Progressive Disclosure

Section structure is clear and the bulky per-provider tracking material is externalized via clearly labeled, one-level-deep links; however, the inline provider-conversion table and ~55 lines of Python snippets are borderline reference material, and the linked files live in a sibling skill (../built-in-metrics/) that could not be verified here (no references/, scripts/, or assets/ directories exist in this bundle).

4 / 5

Total

18

/

20

Passed

Description

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

The description communicates concrete capabilities in a specific domain, but it lacks any explicit "when to use" trigger guidance and slips into second-person voice ("Helps you identify"), both of which the rubric penalizes. Trigger terms are good though not comprehensive.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding function calling / tools to an LaunchDarkly agent config, or when the user mentions attaching tools to a variation."

Rewrite in third person to remove "you"/"your" (e.g. "Identifies needed capabilities, creates tool definitions, and attaches them to config variations").

Include a few more natural synonyms such as "tool calling" or "function definitions" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"identify what your agent needs to do, create tool definitions, and attach them to config variations" lists three concrete actions (an anchor-4 pattern), but the phrasing "Helps you identify" uses second-person voice, which the guidelines penalize by reducing specificity by 1.

3 / 5

Completeness

The "what" is clear (create tool definitions, attach to config variations), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "tools", "function calling", "tool definitions", and "config variations" are present and would be said by users needing this skill, but common synonyms such as "tool calling" or "function definitions" are missing.

4 / 5

Distinctiveness Conflict Risk

"attach them to config variations" plus the LaunchDarkly tooling context carves out a distinct niche with only minor overlap risk against generic agent-tooling skills; it is not fully at the anchor-5 level because "tools (function calling)" alone is broad terminology in the agent space.

4 / 5

Total

14

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 5 suspicious

Warning

Total

15

/

16

Passed

Repository

launchdarkly/ai-tooling

Path

skills/agentcontrol/tools/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.