Task Development Workflow
v1.0.0TDD-first development workflow with structured planning, task tracking, and PR-based code review. Use when building software projects that require clarificat...
⭐ 0· 1.9k·25 current·26 all-time
byMd. Mushraful Hoque Anik@anikgnr
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (TDD-first task workflow, Trello task tracking, PR-based review) matches the actual instructions. All required actions are process and human-workflow steps (planning, tests, branches, PRs, Trello card moves). There are no unrelated environment variables, binaries, or config paths requested.
Instruction Scope
SKILL.md and references only give procedural guidance (questions to ask, TDD steps, Trello board columns, PR templates, branch rules). It does not instruct the agent to read system files, environment variables, or send data to external endpoints. One operational note: it mentions 'push force with lease' as a conflict resolution step (an operational risk to repository history if used improperly) but that is a process recommendation rather than hidden automation or exfiltration.
Install Mechanism
No install spec and no code files — this is instruction-only, which is the lowest-risk install surface. Nothing will be downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It references Trello and Git workflows but does not request Trello/GitHub tokens or other secrets; if you later automate parts of this workflow, you will need to supply appropriate scoped credentials separately.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills/configuration. Autonomous invocation is allowed by default on the platform, but this skill contains only guidance and cannot perform privileged actions on its own.
Assessment
This is a guidance-only workflow (no code, installs, or credential requests) and is internally consistent with its stated purpose. It appears safe to use as a process checklist. Two practical cautions: (1) the publisher/source and homepage are missing—prefer skills with identifiable provenance if that matters to you, and (2) if you later attach automation (e.g., scripts that integrate with Trello or GitHub), only grant minimal-scoped credentials and be careful with force-push operations, which can rewrite repository history.Like a lobster shell, security has layers — review code before you run it.
latestvk9732yr2t1hf1k2scw91xpbags8198c9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.