Better
v1.0.0Better Mortgage PM work context. Senior PM role leading borrower communications team (call routing, dialers, CRM systems, speed-to-lead optimization). Use wh...
⭐ 0· 144·0 current·0 all-time
byTej Wadwa@tw0316
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description (Better Mortgage PM context) matches the SKILL.md content (role, tools, responsibilities, typical requests). It requires no binaries, env vars, installs, or code, which is proportionate to a context/persona skill.
Instruction Scope
SKILL.md is limited to role context, tools, workflows, and behavior instructions (e.g., be concise). It does include sensitive personal/compensation details (base salary, bonus, RSUs, vesting dates). While these are coherent with a personal work-context skill, they are sensitive and you should consider whether you want them stored/used by the agent or shared with others.
Install Mechanism
No install spec and no code files — lowest risk. Nothing is written to disk or downloaded by the skill itself.
Credentials
The skill requests no environment variables, credentials, or config paths. It mentions tools (MS Teams, Outlook, Confluence, JIRA, Athena) as relevant context but does not request access to those services' credentials, which is appropriate for a context-only skill.
Persistence & Privilege
always:false and no special privileges requested. The skill can be invoked by the model (platform default) but does not request permanent elevated presence or modify other skills.
Assessment
This skill is internally consistent and appears safe from a permissions perspective, but note it contains personal and compensation details (salary, RSUs, vest dates). Only install or enable it in an agent you control and trust. If you plan to share the skill or use it in a multi-user/org agent, consider redacting or removing sensitive items, confirm the skill's origin (source/homepage are unknown), and limit visibility. If the agent will access external services (Teams/Outlook/JIRA) later, grant those credentials separately and explicitly rather than embedding them in a context skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97294s92wmvkvzq2hhg1nrm9s835pe0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.