cooper-email
Give Claude its own email inbox with Cooper Email to send, receive, reply, and wait for replies or verification codes over a hosted MCP server or HTTP. Use when the user wants the agent to have its own email address, not access to the user's mailbox.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow monitors and consumes incoming email messages from an external email service, which allows outsider-authored free text injection.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
The skill configures the agent to connect to an external hosted MCP server and HTTP API at cooperemail.com, but this is an unverified third-party service rather than a recognized first-party publisher, constituting a weak/unknown operational dependency.
- Repository
davepoon/buildwithclaude
- Revision
50fc3a8
- Audited
- Security analysis
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.