DoctorClaw Project Status
AdvisoryAudited by Static analysis on May 3, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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 skill may read task and project information from connected services or files.
The skill needs access to task or project systems, which may involve user or workspace account data. This is expected for a project-status dashboard, but users should scope access carefully.
- **Task system** — Any task/project source: Todoist, Asana, Notion, Trello, Linear, plain text files, or CSV
Connect only the project sources needed for the dashboard and prefer read-only or least-privilege access where available.
Private project details could be posted to the wrong chat or a channel with broader membership than intended.
The skill can send generated project status to an external messaging channel. This is disclosed and user-configured, but the report may contain sensitive project, workload, blocker, or client information.
- **Delivery channel** — Telegram/Discord for daily status updates ... - Send status board via configured channel
Verify the destination channel, audience, and content before enabling automated delivery.
Archived reports may preserve internal project, team, and deadline information beyond the immediate session.
The skill stores status reports in persistent memory so future reports can use historical trends. This is useful for the stated purpose, but it retains potentially sensitive project data.
- Save to `memory/project-status/YYYY-MM-DD.md` - Track project health trends over time
Set retention expectations, avoid storing unnecessary sensitive details, and periodically review or delete archived status files.
Reports or alerts may continue to be generated automatically until the schedule is changed or removed.
The skill supports scheduled recurring operation. This is disclosed and central to the daily status-board use case, but scheduled tasks can continue running after setup.
Run it daily on a cron ... Report schedule — when to generate (default: every morning at 8:30 AM)
Confirm the schedule, know how to disable it, and make sure automated alerts go only to approved recipients.