Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Pipeworx could-have-been-email

v1.0.0

Analyzes meeting transcripts to determine if the discussion could have been an email, returning filler word count and decisions.

0· 74· 1 versions· 0 current· 0 all-time· Updated 5d ago· MIT-0
byBruce Gutman@brucegutman

Could Have Been Email

could-have-been-email MCP — wraps StupidAPIs (requires X-API-Key)

could_have_been_email_analyze

Check if a meeting transcript could have been an email instead. Returns filler word count, decisions

{
  "mcpServers": {
    "could-have-been-email": {
      "url": "https://gateway.pipeworx.io/could-have-been-email/mcp"
    }
  }
}

Version tags

latestvk97dw8yhqyahhbd4crg9xxrbtn85c66j