CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webhook-trigger

POST Aegis events to webhook URLs

Quality

62%

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

55%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 commendably lean and well-structured, but it stops at environment setup and gives no executable usage guidance or workflow for the actual webhook triggering, leaving Claude without the steps to run the skill.

Suggestions

Add a short 'Usage' section with an executable command showing how to invoke scripts/webhook.py (e.g. the --webhook-url / --secret / --config flags it accepts) and a sample event payload.

Document the event flow (read JSON from stdin, POST matching events, emit webhook_sent/error) so the workflow is sequenced rather than implied.

Either add the missing requirements.txt referenced in Setup or replace the pip install line with the actual dependency (e.g. pip install requests) so the setup block is reproducible.

DimensionReasoningScore

Conciseness

The body is extremely lean — a one-line purpose statement plus a Setup block — with no padding or explanation of concepts Claude already knows, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

Only setup commands (venv, pip install) are executable; the body never shows how to actually run scripts/webhook.py, what arguments it takes, or what event payloads look like, fitting 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'; it is not score 3 because there is no executable usage example at all, only environment setup.

2 / 5

Workflow Clarity

The body covers only a rough setup sequence and omits the core trigger workflow (how events are received, posted, and verified), matching 'Rough sequence present but many gaps; steps poorly defined'; it is not score 3 because no operational steps or checkpoints for the actual webhook posting are described.

2 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (title, intro, Setup) and the referenced scripts/webhook.py exists, matching 'Good structure; most content appropriately placed; minor organization gaps'; it is not score 5 because requirements.txt is referenced but absent from the bundle.

4 / 5

Total

13

/

20

Passed

Description

53%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 concise and states a concrete capability with a distinct Aegis-specific niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when posting Aegis events to Zapier, IFTTT, Make, n8n, or custom webhook endpoints').

Include synonyms and file/protocol terms users might say ('webhooks', 'HTTP callback', 'automation integration') to raise trigger-term coverage.

List one or two more concrete actions (e.g. 'with X-Aegis-Secret authentication, retries') to move specificity toward comprehensive.

DimensionReasoningScore

Specificity

The phrase 'POST Aegis events to webhook URLs' names the domain (webhooks) and one concrete action (POST events), matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor; it is not score 4 because only a single action is listed with no broader coverage.

3 / 5

Completeness

The description clearly states what the skill does ('POST Aegis events to webhook URLs') but provides no 'Use when...' trigger guidance, so per the rubric a missing trigger clause caps completeness at 3 ('clear what but when missing or only weakly implied').

3 / 5

Trigger Term Quality

'webhook URLs' and 'Aegis events' are relevant natural terms, but coverage stops there with no synonyms or variations, fitting 'Some relevant keywords but missing common variations or synonyms'; it is not score 4 because common variants like 'webhooks', 'HTTP callback', or 'integration' are absent.

3 / 5

Distinctiveness Conflict Risk

The combination 'Aegis events to webhook URLs' carves a fairly distinct niche with minimal overlap risk, matching 'Mostly distinct; minor overlap risk with closely related skills'; it is not score 5 because 'webhook' alone is a broadly shared term that could lightly overlap with other integration skills.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

SharpAI/DeepCamera

Path

skills/automation/webhook/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.