!
Purpose & Capability
The skill's stated purpose is to send applications via Gmail. The code indeed sends mail, manages local application records, and creates Gmail labels — so capability matches purpose. However the SKILL.md and registry metadata do not consistently declare required credentials: SKILL.md lists GMAIL_API_KEY while the code expects MATON_API_KEY. The registry lists no required env vars. This mismatch (and a hard-coded API key in the code) is incoherent and unnecessary for a transparent integration.
!
Instruction Scope
SKILL.md triggers on job-related keywords and instructs automatic sending, labeling, and CCing of records. The code implements that and also sends data (email content, attachments) to a third-party gateway (gateway.maton.ai). SKILL.md refers to Gmail integration but does not disclose use of this third-party gateway or the hard-coded credential; automatic activation + external network calls expands the attack surface and is not fully transparent.
✓
Install Mechanism
There is no install spec (instruction-only), so nothing is downloaded or installed by an installer. The only code is included in the bundle (scripts/send_application.py) which will run if invoked — no external install URLs or extracted archives were found.
!
Credentials
The skill metadata lists no required env vars, SKILL.md mentions GMAIL_API_KEY and other config keys, but the script actually uses MATON_API_KEY and provides a long default hard-coded value. Embedding a default API key in code is a serious red flag: it grants the included third-party service access to sent messages/attachments. The required/declared env vars are inconsistent with what code uses, and the hard-coded credential is disproportionate to a transparent Gmail integration.
✓
Persistence & Privilege
always:false and no special OS restrictions. The skill does not request permanent platform-level presence and does not modify other skills or system-wide agent settings. Autonomous invocation by the agent is enabled (default) but not combined with other privileged flags.
Scan Findings in Context
[hardcoded-maton-api-key] unexpected: The script defines MATON_API_KEY with a long default value inside the code. A mailing/Gmail integration should not ship with a reusable secret; this may permit the bundled third‑party gateway to access emails/attachments.
[third-party-mail-gateway] unexpected: Instead of calling official Google/Gmail APIs or describing OAuth flows, the code posts to https://gateway.maton.ai/google-mail/..., a third‑party gateway. The SKILL.md mentions Gmail but does not disclose use of this gateway or any privacy/consent implications.
[env-var-name-mismatch] unexpected: SKILL.md references GMAIL_API_KEY but the script reads MATON_API_KEY and the registry lists no required env vars. This mismatch is a transparency / configuration bug that could lead users to expose credentials unintentionally.
What to consider before installing
This skill's functionality (compose and send application emails, manage local records) is coherent, but there are important red flags you should address before installing or using it:
- Do not rely on the hard-coded MATON_API_KEY in the script. Treat it as a secret: remove it from code and require the user to provide their own credential (and prefer OAuth for Gmail). If you already used this code with the embedded key, consider revoking that key at the Maton/gateway service.
- Verify and understand the third-party gateway (gateway.maton.ai). The script sends email content and attachments through that service; only use it if you trust that provider and their data handling. Prefer using Google's official API and OAuth flows if you want direct Gmail integration.
- Fix the configuration inconsistencies: SKILL.md, registry metadata, and the code should agree on what env var is required (e.g., GMAIL_API_KEY or MATON_API_KEY) and declare it in the registry. Avoid shipping default credentials.
- Review the code for how attachments are selected (resume path) so you don’t unintentionally send sensitive files. The script reads data/resume.json and local resume file paths — ensure those files contain only information you want transmitted.
- If you do not trust the Maton gateway or the embedded key, do not run the send functionality. You can still use the non-network parts locally (cover letter generation, local application tracking) after removing or sandboxing network calls.
If you want, I can suggest precise code changes to remove the hard-coded key, add explicit env var checks, or switch the script to use OAuth with Google's official API.
