customer-success-triage — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited customer-success-triage (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Triage customer-success work. $ARGUMENTS should contain the client name or ID, plus an optional focus area.
Use the LifeOS MCP tools in this order:
get_client_success_workspace with the client from $ARGUMENTS.recentThreadsrecentMeetingsnotesopenTasksprojectsget_beeper_thread_messagesget_fathom_meeting, get_fathom_transcriptget_granola_meeting, get_granola_transcriptget_client_notesget_belief_reframes with projectIds to surface linked fears, inversions, and limiting-belief friction records before deciding what is blocked or risky.get_project_graph for the relevant project because it includes PPV context and belief_reframe friction nodes. Use FalkorDB only for sidecar traversal or agent-owned relationship links.falkor_graph_link only for durable agent-owned relationships with reason and confidence.Classify findings into:
Use writes deliberately:
create_client_note or update_client_notecreate_issue or update_issue only for execution workPresent the result as:
If the user did not explicitly ask you to make changes, ask for confirmation before any write operation.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.