CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

managing-agent-webhooks

Creates, lists, tests, enables, disables, rotates, inspects, and deletes inbound webhooks for the current Letta Cloud agent. Use when a user asks to set up a webhook, send external events to an agent, test webhook delivery, inspect recent webhook requests, rotate a webhook URL, or remove a webhook.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, with executable commands, verified script references, strong safety guidance, and a workflow that includes genuine validation and reconciliation loops. Its main weakness is token efficiency: ambiguity-handling rules are repeated across Safety and Errors, and the helper's internal sanitization mechanics are documented at a level of detail the calling agent does not need.

Suggestions

Consolidate the repeated ambiguity/reconcile guidance into a single place (e.g. the Errors section) and reference it from Safety instead of restating create/delete/rotate rules twice.

Trim or summarize the ~15 lines describing the helper's internal sanitization pipeline (recursive redaction, structural redaction, 1 MiB caps) down to the behavioral contract the agent needs: 'the helper redacts secrets and caps output; never print credential files'.

Consider moving deep error-edge-case detail (response validation rules per operation, canonical-URL checks) into a references/ file kept one level deep, keeping SKILL.md to the workflow and command invocations.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows, but the ~100-line Safety section restates ambiguity/reconcile guidance multiple times (ambiguous-create retry rules appear both in Safety and again under Errors, delete confirmation rules are given twice) and lines 36-52 detail the helper's internal sanitization mechanics that the agent invoking the CLI does not need. This fits anchor 3 ('mostly efficient but could be tightened') rather than 4, since the redundancy and implementation detail go beyond minor trimming.

3 / 5

Actionability

Every command is a complete, copy-paste-ready invocation with real flags and realistic values (e.g. the full create command with --name/--preprompt/--secure/--credential-output, stdin piping for user-supplied keys, test commands with --confirm), plus concrete error-code interpretations (404 with errorCode check, 401, 202 semantics). Fully executable guidance covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The Workflow section gives a clearly sequenced 6-step process (list first to avoid duplicates, establish name/preprompt/auth mode, create and deliver the credential, consent-gated test, report 202 as accepted only, explain async behavior) with explicit validation checkpoints and error-recovery feedback loops (reconcile by name via list before retrying an ambiguous create, list before treating a delete as confirmed). This matches the anchor-5 example pattern of sequence plus explicit validation and recovery loops.

5 / 5

Progressive Disclosure

The single bundle script is referenced consistently and correctly via <SKILL_DIR>/scripts/manage-agent-webhooks.mjs (all referenced flags exist in the actual file), and sections (Safety, Environment, Workflow, Commands, Errors) are clearly organized. However, the 320-line body inlines a dense ~100-line block of internal redaction/validation and error-edge-case detail that could partly live in a separate reference file, so it fits anchor 4 ('minor organization gaps') rather than 5, given the skill exceeds the under-50-line simple-skill case.

4 / 5

Total

17

/

20

Passed

Description

92%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 is strong: it enumerates the full webhook lifecycle with concrete third-person verbs, explicitly scopes the target (current Letta Cloud agent), and pairs the capability list with an explicit 'Use when' clause containing natural trigger phrases. The only weakness is modest synonym coverage in the trigger terms.

Suggestions

Add common synonyms to the trigger clause, e.g. 'incoming webhook', 'webhook endpoint', or 'connect an external integration', so users phrasing the request differently still match.

DimensionReasoningScore

Specificity

"Creates, lists, tests, enables, disables, rotates, inspects, and deletes inbound webhooks for the current Letta Cloud agent" lists eight concrete, specific actions with comprehensive coverage of the capability, matching the anchor-5 example pattern; it is not score 4 because there are no minor gaps in the action list.

5 / 5

Completeness

It explicitly answers both "what" (the eight lifecycle operations on inbound webhooks) and "when" ("Use when a user asks to set up a webhook, ... or remove a webhook") with concrete trigger phrases, exactly matching the anchor-5 structure; score 4 would require the 'when' clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The "Use when" clause covers six natural trigger phrases ("set up a webhook", "send external events to an agent", "test webhook delivery", "inspect recent webhook requests", "rotate a webhook URL", "remove a webhook"), but common synonyms such as "incoming webhook", "webhook endpoint", or "connect an integration" are missing, which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Letta Cloud agent" webhook lifecycle management is a clearly delineated niche with distinct triggers (webhook setup, delivery testing, URL rotation, removal), giving minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

letta-ai/letta-code

Path

src/skills/builtin/managing-agent-webhooks/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.