← Back to Skills Marketplace
Project Developer
by
EncryptShawn
· GitHub ↗
· v1.0.2
· MIT-0
124
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install project-dev
Description
Software Developer Project Skill — coordination, workflow, and team interoperation for FE and BE developer agents working on managed software projects. Use t...
Usage Guidance
This skill appears to be a workflow-only coordination tool and is coherent with its description, but before installing you should: 1) Confirm USER.md and TOOLS.md are maintained by the operator and do not contain secrets (repo URLs should not embed credentials). 2) Verify the Git and Asana dependency skills you will pair with this are trusted and scoped with least privilege (Git PATs limited to the intended repos; Asana PAT scoped appropriately). 3) Ask the skill author to clarify what "sessions_send nudges" does and where those nudges are sent/recorded. 4) Consider asking the publisher to add USER.md and TOOLS.md to the package metadata as required config paths (or document them clearly) so operators know the skill will read those workspace files. If those checks look good, the skill's behavior is consistent with its stated purpose.
Capability Assessment
Purpose & Capability
The name/description (developer coordination, Asana queue heartbeat, branch/PR/QA workflow) matches the skill's instructions: it only describes workflow and delegates repo and Asana operations to separate Git/Asana skills. It does not request unrelated binaries, env vars, or credentials in the package metadata. The use of repo URLs, Asana GIDs, and credential label identifiers in USER.md/TOOLS.md is expected for this kind of orchestration skill.
Instruction Scope
Runtime instructions explicitly read operator-managed workspace files (USER.md and TOOLS.md) and instruct the agent to use the installed Asana/Git skills to act on tasks and heartbeat queues. However, the registry metadata lists no required config paths — the SKILL.md references workspace files but the package metadata does not declare them as required. This is a bookkeeping/information inconsistency (the skill will read those files at runtime). Also the skill mentions sending "sessions_send nudges" — the destination/mechanism of that is platform-specific and not fully described; the operator should confirm what that action does and whether it transmits data outside the agent/session.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. Nothing will be written to disk by an installer from this package itself.
Credentials
The skill declares it uses no credentials and only references credential LABELS (for the Git and Asana dependency skills) rather than secret values. That is proportionate for a coordination/workflow skill. Operational caveat: correctness and safety depend on the operator's configuration of the Git/Asana skills and on USER.md/TOOLS.md contents; if those files or the dependency skills are misconfigured they could expose broader access than intended (e.g., repo URLs with embedded creds or over-scoped Git PATs).
Persistence & Privilege
The skill is not 'always' and does not install background timers or persist across sessions; heartbeat scheduling is described as platform-managed. The skill can be invoked autonomously by the agent (default), which is expected for skills of this type and not problematic by itself. No evidence it modifies other skills or system-wide agent settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install project-dev - After installation, invoke the skill by name or use
/project-dev - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
**Summary: Credentials and scheduling are now strictly externalized; workflow clarified as guidance only.**
- Updated to clarify this skill never accesses or manages credentials or tokens; all authentication is handled by dependency skills (Git, Asana).
- Noted that the 30-minute heartbeat is triggered and scheduled by the OpenClaw platform, not by the skill itself.
- Added detailed sections on the trust and workspace file model, explicitly stating that USER.md and TOOLS.md are operator-managed and never contain secrets.
- Restructured documentation around dependency skill usage and clarified that this skill only provides workflow instructions, never executes API calls or stores sensitive information.
- No behavioral changes to developer task workflow or inter-agent coordination.
v1.0.1
**Expanded to support heartbeat task queue checks and API contract coordination across multiple projects.**
- Added Asana heartbeat protocol: every 30 minutes, checks the correct dev queue (FE/BE) for each active project in USER.md and picks up ready tasks.
- Introduced sessions_send protocol for inter-agent coordination: now required for PR handoffs, API contract sharing, and escalation to other roles.
- Clarified FE/BE role separation: branch naming, repo access, and usage of authentication env vars from TOOLS.md.
- Added workflows for handling API contract readiness and frontend/backend interoperation (sessions_send between dev-fe and dev-be).
- Updated blocker escalation and dependency handling: always comment in Asana and sessions_send to PM/Engineer as appropriate.
- Refined task workflow details and emphasized multi-project support for developer agents.
v1.0.0
Initial release: defines developer task workflow and team protocols for managed software projects.
- Clarifies FE/BE developer roles and ownership boundaries within project teams.
- Outlines task lifecycle: assignment, spec review, active work, blocker escalation, self-check, PR creation, QA handoff, and completion.
- Specifies branch naming conventions per role.
- Details required external skills (Git, Asana, tech stack skills) with this skill focused on coordination and workflow.
- Provides explicit escalation and status update procedures to facilitate efficient teamwork.
- you need to install your choice of git, asana and developer tech skills
Metadata
Frequently Asked Questions
What is Project Developer?
Software Developer Project Skill — coordination, workflow, and team interoperation for FE and BE developer agents working on managed software projects. Use t... It is an AI Agent Skill for Claude Code / OpenClaw, with 124 downloads so far.
How do I install Project Developer?
Run "/install project-dev" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Project Developer free?
Yes, Project Developer is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Project Developer support?
Project Developer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Project Developer?
It is built and maintained by EncryptShawn (@encryptshawn); the current version is v1.0.2.
More Skills