Project Tracker
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only project tracker appears purpose-aligned, with the main thing to notice being that it creates persistent local project records and can reuse them in dashboards or memory files.
Before installing, be comfortable with the agent maintaining Markdown records of your projects, priorities, blockers, and decisions. Keep the files in a dedicated folder, review generated weekly reports and pause/kill recommendations as advisory, and avoid storing confidential project details in shared memory unless that is intended.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may create or change Markdown files in the local `projects/` directory as part of normal use.
The skill directs the agent to create and modify local project files. This is expected for a project tracker, but users should know it will edit persistent files.
When the user mentions a new project, create `projects/<project-name>.md` ... Update `projects/DASHBOARD.md` whenever:
Keep the tracker scoped to a dedicated `projects/` directory, review important file changes, and avoid using unsafe project names as filenames.
Project decisions, blockers, priorities, and business context may persist beyond the current conversation and influence later recommendations.
The skill may persist project decisions into a memory system, where they could be reused in future tasks. This is purpose-aligned but can include sensitive business or personal planning information.
With memory system: Log project decisions in daily memory files
Do not store sensitive strategy or confidential stakeholder details unless you are comfortable with them being reused by the memory workflow; periodically review and clean old project memory entries.