CtrlK
BlogDocsLog inGet started
Tessl Logo

webhook-trigger

POST Aegis events to webhook URLs

56

Quality

64%

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/automation/webhook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is admirably lean and well-structured for a simple skill, but it stops at setup and never shows how to actually run the trigger or verify it works, which limits actionability and workflow clarity.

Suggestions

Add a runnable usage example, e.g. `python scripts/webhook.py --webhook-url https://... --secret ...`, showing how the trigger is invoked.

Include the expected event flow (stdin JSON lines in, webhook_sent/error events out) and a verification step so the workflow has a checkpoint.

Either provide the referenced requirements.txt or replace the `pip install -r requirements.txt` line with an explicit `pip install requests` to avoid a dangling reference.

DimensionReasoningScore

Conciseness

The body is lean — one descriptive sentence plus a setup block — with no padding or explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

The setup commands are executable, but the body gives no example of how to run the trigger (e.g., invoking scripts/webhook.py with its arguments) and references a requirements.txt that is not present in the bundle, leaving key details missing.

2 / 3

Workflow Clarity

Only environment setup is shown; the actual run/usage flow and any validation or error-handling checkpoint are absent from the body, so the sequence is incomplete.

2 / 3

Progressive Disclosure

The skill is under 50 lines with well-organized sections (overview + Setup) and the implementation appropriately externalized to scripts/webhook.py one level deep, fitting the simple-skill anchor.

3 / 3

Total

10

/

12

Passed

Description

57%

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 concrete and occupies a distinct niche, but it stops at a single action and omits any explicit trigger guidance, leaving it mid-range on completeness and trigger coverage.

Suggestions

Add an explicit "Use when..." clause naming natural trigger terms (e.g., 'Use when forwarding Aegis events to Zapier, IFTTT, Make, n8n, or custom webhooks').

Expand the action list beyond a single POST to reflect the concrete capabilities (e.g., 'POST Aegis clip, detection, and alert events as JSON to webhook URLs').

Surface the integration names (Zapier, IFTTT, Make, n8n) in the description itself to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase "POST Aegis events to webhook URLs" names a concrete action and domain, but it is a single action rather than the multiple specific actions the score-3 anchor requires.

2 / 3

Completeness

It clearly states what the skill does ("POST Aegis events to webhook URLs") but lacks any "Use when..." trigger guidance, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

"webhook URLs" is a natural keyword, but the common integration variations (Zapier, IFTTT, Make, n8n) appear only in the body, not the description, so coverage of natural terms is incomplete.

2 / 3

Distinctiveness Conflict Risk

The Aegis-events-to-webhook niche is specific and unlikely to overlap with other skills, matching the clear-niche anchor.

3 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
SharpAI/DeepCamera
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.