Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chunkydotdev/inbound-processing
Receive, parse, and process incoming email via provider webhooks.
Passed 19 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed15 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are implementing a weighted scoring system for prompt injection detection in inbound email text. Which specific attack category carries the highest individual weight (0.60) in the pattern scoring model?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns system prompt mimicry the maximum risk weight of 0.60. | Missed | Passed |
The instructions your model reads when the skill loads.
Receive incoming email, parse it into structured data, and route it to the right place.
domain-authentication - SPF/DKIM/DMARC setup that affects inbound auth verificationreply-classification - classifying reply intent (interested, OOO, objection, etc.)thread-management - maintaining full conversation context across messageswebhook-processing - general webhook handling patterns (retries, idempotency)email-security - injection attacks, content sanitization, phishing preventionbounce-handling - processing delivery failures from outbound sendsWhen someone sends an email to your domain, it hits an MX server. You have two options:
The provider handles MX record reception, MIME parsing, spam pre-filtering, and delivers a clean JSON payload to your endpoint. You handle business logic.
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.