Menú
Pull meld status and full message thread via pm-get-comments.py before taking any action on a meld. Single-meld context fetch.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
When pm probe returns 401/403 (session expired), automatically recapture PropertyMeld session cookies. macOS agents use the AX+CDP script; Linux/cloud agents use the Playwright headless script.
How to install and operate snapcli-pm for Property Meld. Covers tool hierarchy, install, and non-obvious operational rules. Run 'pm --help' or 'pm work-orders --help' for the live command list.
When a meld contains multiple interdependent or multi-trade work items, decompose it into parallel and sequential workstreams before acting. Prevents dispatching trade A before trade B's prerequisite work is done.
Triage rules playbook for Property Meld work orders. Determines urgency, routing, and suppression rules before any action is taken.
After every meld decision, capture what was decided and why (trajectory). Weekly: scan all trajectories for override patterns, surface refinement candidates to Dane.
After completing a complex task, check whether the sequence of steps used represents a recurring pattern worth codifying into a skill. Logs skill candidates to the bus for weekly review by Dane.
| name | pm-check-meld |
| effort | low |
| description | Pull meld status and full message thread via pm-get-comments.py before taking any action on a meld. Single-meld context fetch. |
| triggers | ["check meld","pull meld","get meld comments","what's the status on meld","read meld thread","look at meld"] |
Always run this before triaging, responding to, or escalating a meld. Never act on subject line alone.
python3 scripts/pm-get-comments.py <meld_id>
Output: JSON with meld metadata + full message thread, printed to stdout.
From the output, note:
| Field | Where to find it | Why it matters |
|---|---|---|
| Current status | status field | Is it already assigned, scheduled, or resolved? |
| Vendor assigned | vendor or assigned_to | Is someone already on it? |
| Last comment author | Last entry in comments[] | Did Brittany or a vendor already respond? |
| Last comment timestamp | comments[-1].created_at | How recent is the last activity? |
| Tenant last message | Scan comments[] for tenant author | Is tenant escalating, or satisfied? |
| Scheduled date | scheduled_date or comment mention | Is an appointment already booked? |
If the last comment is:
| Error | Meaning | Action |
|---|---|---|
| Script exits non-zero | Session or login failure | Log meld_poll_blocked, message Dane with stderr |
Empty comments array | Meld has no thread yet | Proceed to triage on meld metadata only |
login in redirect URL | Cookie expired | Script handles fresh login automatically; retry once |
Feed results into pm-meld-triage skill:
Read pm-meld-triage SKILL.md and classify meld <id> based on:
- Status: <status>
- Vendor: <assigned or none>
- Last activity: <timestamp> by <author>
- Thread summary: <1-2 sentence summary>
To check multiple melds (e.g. during morning scan), loop:
for MELD_ID in 12345 12346 12347; do
echo "=== Meld $MELD_ID ==="
python3 scripts/pm-get-comments.py $MELD_ID
echo ""
done
Run this first. Always. It's one script call and prevents false escalations.