Better

v1.0.0

Better Mortgage PM work context. Senior PM role leading borrower communications team (call routing, dialers, CRM systems, speed-to-lead optimization). Use wh...

0· 221·0 current·0 all-time
byTej Wadwa@tw0316

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for tw0316/better.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Better" (tw0316/better) from ClawHub.
Skill page: https://clawhub.ai/tw0316/better
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install better

ClawHub CLI

Package manager switcher

npx clawhub@latest install better
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & 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
221downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Better - Day Job Context

Context for Tej's Senior PM role at Better Mortgage.

Role

  • Title: Senior PM, Borrower Communications
  • Focus: Call routing, dialers, CRM systems, speed-to-lead optimization
  • Team: Leads a team focused on lead intake → loan officer connection
  • Start Date: December 2, 2024
  • Compensation: $217K base + 15% bonus + 3,200 RSUs (4yr vest, quarterly, granted $10, current $29)
  • First RSU vest: March 2, 2025 (800/yr = 200/quarter)

Work Boundaries

  • This is the W2 that funds everything else
  • Takes it seriously, but it's a vehicle not a destination
  • Don't pollute with startup/RE context — keep work clean

Tools

  • MS Teams
  • Outlook
  • Confluence
  • JIRA
  • Athena

Typical Requests

  • Meeting prep (e.g., "Pull agenda for tomorrow's standup")
  • Project status updates
  • Team coordination
  • Metrics analysis (speed-to-lead, conversion rates)
  • Workflow documentation

Principles

  • Efficiency and effectiveness are core values
  • Tej is bandwidth-constrained — optimize for his time, not completeness
  • Direct answers, no fluff

Comments

Loading comments...