Dev Project Manager
v1.0.0Comprehensive AI Project Manager skill for software development. Use this skill whenever the PM agent needs to: engage with clients about new or existing sof...
⭐ 0· 63·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description match the runtime instructions and reference templates: it is a PM workflow/templating skill that coordinates with an engineer and an Asana integration (explicitly delegating API calls to a separate asana skill). It requests no unrelated binaries, env vars, or config paths.
Instruction Scope
SKILL.md and the reference files confine activity to requirements elicitation, technical-assessment coordination, SRS and change-management templates, and UI comparison requests to engineers. It does not instruct reading unrelated system files or exfiltrating secrets. Note: the skill contains broad trigger conditions (many PM-related keywords) which may cause frequent invocation if enabled.
Install Mechanism
No install spec and no code files — instruction-only skill, so nothing is written to disk or downloaded during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. All templates and protocols are local instructions; there are no unexpected requests for tokens/keys.
Persistence & Privilege
always is false and model-invocation is allowed (default). The skill does not request persistent system-level privileges or modifications to other skills' configurations.
Assessment
This skill appears coherent and matches its PM purpose, but before installing consider: (1) it coordinates with an 'engineer' agent and expects that agent (or other skills) may need access to codebases or screenshots — confirm which agents will receive project data and whether those agents have appropriate access controls; (2) Asana API interactions are explicitly delegated to a separate asana skill — ensure you install/configure that skill (and its credentials) if you want automated board/task changes; (3) templates include opinionated defaults (hourly rates, token-cost assumptions) — review and adjust those before using them with clients; (4) the skill's broad trigger list may cause frequent activations — review trigger settings and invocation policies to avoid noisy or accidental runs.Like a lobster shell, security has layers — review code before you run it.
latestvk978yh2tkrvd3kg74as9ex848184pkha
License
MIT-0
Free to use, modify, and redistribute. No attribution required.