CtrlK
BlogDocsLog inGet started
Tessl Logo

webhook-transforms

Generic framework for converting external events (SMS, meetings, social mentions) into brain-ingestible signals. Define a transform function, register a webhook URL, and incoming events get processed through the brain pipeline.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/webhook-transforms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The skill is well-structured with a clear sequence and good error-handling intent, but it stops short of executable transform code and lacks an explicit validation checkpoint before brain writes, while carrying minor redundancy between the Contract and Phases sections.

Suggestions

Provide at least one executable transform function example (real code mapping a sample payload to a brain page) instead of input/output prose blocks.

Add an explicit validation step before the brain write (e.g. verify sanitized output and required metadata are present, then write) so the workflow has a pre-write checkpoint.

De-duplicate the Contract and Phases sections — keep guarantees in the Contract as one-line promises and reserve the how-to detail for Phases.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of concept explanation Claude already knows, but the Contract bullets restate sanitization and error-handling details already covered in Phases 1 and 4, adding mild redundancy that could be tightened.

2 / 3

Actionability

Concrete commands appear ('gbrain put', 'gbrain sync') and steps are specific, but the Example Transforms are illustrative input/output blocks rather than executable transform functions, leaving the core logic as description rather than copy-paste code.

2 / 3

Workflow Clarity

The four phases are clearly sequenced with an error-recovery loop (dead-letter queue, retry once), but there is no explicit validation/verification checkpoint before the mutating brain write, which caps clarity at 2 for a batch/mutating workflow.

2 / 3

Progressive Disclosure

No bundle files are present or needed; the body is well-organized into clearly labeled sections (Contract, Phases, Example Transforms, Output Format, Anti-Patterns), satisfying the simple-skill threshold for progressive disclosure.

3 / 3

Total

9

/

12

Passed

Description

60%

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 states concrete capabilities and a clear domain, but omits explicit trigger/usage guidance and leans on internal jargon that weakens natural-language triggering and distinctiveness.

Suggestions

Add an explicit 'Use when ...' clause listing natural triggers such as 'Use when setting up webhooks, processing incoming SMS/meeting/social events, or converting external events into brain signals.'

Replace internal jargon ('brain-ingestible signals', 'brain pipeline') with user-facing terms and add common variations like 'webhooks' and 'incoming events'.

Sharpen distinctiveness by contrasting with sibling ingest skills (e.g. note that raw meeting transcripts delegate to meeting-ingestion).

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Define a transform function, register a webhook URL, and incoming events get processed through the brain pipeline' — naming the domain (SMS, meetings, social mentions) and specific steps.

3 / 3

Completeness

Clearly answers 'what' but lacks an explicit 'Use when...' or equivalent trigger clause, so 'when' is only implied; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms like 'SMS, meetings, social mentions' and 'webhook', but leans on jargon ('brain-ingestible signals', 'brain pipeline', 'transform function') and misses common variations users would say such as 'webhooks' or 'incoming events'.

2 / 3

Distinctiveness Conflict Risk

The webhook/external-event niche is fairly distinct, but 'brain pipeline' ingestion could overlap with related ingest skills (e.g. the meeting-ingestion skill the body delegates to), so it is not unambiguously conflict-free.

2 / 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
garrytan/gbrain
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.