Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Project
v1.0.0The AI project manager that never forgets, never drops a task, and never lets a deadline sneak up on anyone. Break any goal into phases, tasks, and milestone...
⭐ 0· 382·5 current·5 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The description promises automated tracking across people, teams, chats and external work data (escalations, status reports, updates from conversation). Yet the registry metadata declares no required environment variables, config paths, or install steps for integrating with chat systems, email, calendars, or PM tools. Either the skill relies on platform-provided connectors (not documented here) or the manifest omits necessary capabilities.
Instruction Scope
The SKILL.md explicitly says the skill updates trackers 'when you mention in a chat', logs blockers from team messages, escalates when owners don't respond, and generates status reports from 'actual work data'. Those behaviors imply reading and writing conversational and cross‑system data. The instructions as shown do not document what data sources will be read, where data is stored, or what endpoints messages/notifications are sent to.
Install Mechanism
This is an instruction‑only skill with no install spec and no code files, so there is nothing being downloaded or written to disk by the skill package itself — that is the lowest technical install risk. However, runtime integrations (connectors/APIs) would introduce risk if they exist but are undocumented.
Credentials
No environment variables or credentials are declared, yet the skill's behavior implies it will need access to chat systems, email/calendars, or PM tools. That mismatch is proportionally concerning because access to those services would require tokens/permissions and could expose sensitive data if not clearly specified and limited.
Persistence & Privilege
The skill is not marked always:true and does not request persistent installation behavior in the manifest. Autonomous invocation is allowed (platform default), which increases impact if the skill is later granted broad data access, but that alone is not an immediate coherence issue.
What to consider before installing
This skill's description says it will read chats, detect blockers, escalate, and generate reports from ‘actual work data’, but the package metadata lists no integrations, credentials, or install steps. Before installing or enabling it, ask the publisher (or the platform) for specifics: which systems it will read/write (Slack, Teams, email, calendar, GitHub, Jira, etc.); what credentials/tokens are required; where data and reports are stored; how long data is retained; and what user consent/opt-out controls exist. If the skill needs access to chat or email, treat that as sensitive: verify least-privilege tokens, audit logs of actions, and the ability to revoke access. If the full SKILL.md contains concrete API calls or endpoints, share that so the manifest can be re-evaluated — the current mismatch is the reason for caution.Like a lobster shell, security has layers — review code before you run it.
latestvk977e1w213w92jf6c4jgmnjcd982kfapmanagementvk977e1w213w92jf6c4jgmnjcd982kfapmilestonesvk977e1w213w92jf6c4jgmnjcd982kfapprojectvk977e1w213w92jf6c4jgmnjcd982kfaptasksvk977e1w213w92jf6c4jgmnjcd982kfapteamsvk977e1w213w92jf6c4jgmnjcd982kfap
License
MIT-0
Free to use, modify, and redistribute. No attribution required.