project-status 100/100

Is project-status safe to install?

SaferSkills independently audited project-status (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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/project-status/SKILL.md · 1 file

skills/project-status/SKILL.md1.7 KB · Markdown

name: project-status

description: Project status report with phases, task breakdown, blockers, and urgent items

Get project status. $ARGUMENTS should be a project key like "ACME" or project name.

Use the LifeOS MCP tools:

Call get_project with the project key/ID from $ARGUMENTS
Call get_phases for the project to see phase breakdown
Call get_tasks filtered by the project ID to see all issues
Call get_belief_reframes with projectIds: [project._id] to surface linked fears, inversions, and limiting-belief friction records.
When the user asks how this project connects to PPV, prefer get_project_graph because it includes PPV context and belief_reframe friction nodes.
Use FalkorDB only for sidecar PPV/project traversal or agent-owned graph links: call falkor_graph_schema, then falkor_graph_query; use falkor_graph_link with a clear reason and confidence only for missing durable relationships. Do not mutate project fields through FalkorDB.

Present a project status report:

Overview: Name, status, health, priority, client (if linked)
Phases: Each phase with status and issue counts
Task Breakdown: Count by status (backlog / todo / in_progress / in_review / done)
Urgent/Overdue: Any urgent or overdue tasks
In Progress: What's actively being worked on
Blockers: Anything that looks stuck
Fears / Inversions: Linked friction records that may explain risk, avoidance, or operating constraints
Graph Context: Any FalkorDB sidecar relationships that explain why this project matters or what it connects to

If no project is specified in $ARGUMENTS, call get_projects and list all active projects, then ask which one.

project-status— agent skill

Is project-status safe to install?

Audit the pieces. Scan the whole. Decide.