Is divide-task safe to install?

SaferSkills independently audited divide-task (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/divide-task/SKILL.md · 1 file

.claude/skills/divide-task/SKILL.md1.9 KB · Markdown

name: divide-task

description: Divide a specced pastiche task into sub-task GitHub issues with autonomy and dependency labels, mirror them into `_dev/TODO.md`, and update the parent issue. Use after `grill-to-spec` completes for a task, or when the user invokes `/divide-task`.

divide-task

Harness conventions: _dev/docs/harness.md. Requires: task spec written, task [WIP], feature branch checked out.

Workflow

Derive sub-tasks from the spec. Each sub-task is one implementation step, sized for a single overnight session. Number them N.1, N.2, … where N is the task's TODO number.

Analyze each sub-task:

Autonomy — purely mechanical, mergeable without human judgment → autonomous-ready; otherwise → decision-needed. When in doubt, decision-needed.
Dependencies — which sub-tasks must land first. Independent sub-tasks that touch disjoint files/logic may run in parallel; note the execution order.

Review with the user before creating anything: list sub-tasks, labels, and dependency order. Adjust until approved.

Create child issues. For each sub-task:

Title [N.x] <name>; body: one-paragraph scope + pointer to the spec path; same milestone as the parent; autonomy label.
For blocked ones: create blocked-by-<blocker-issue-number> labels on demand (gh label create) and apply them. Blockers must be created first so their issue numbers exist.
Link each as a sub-issue of the parent (GitHub sub-issue, or a task-list in the parent body if unavailable).

Mirror into `_dev/TODO.md`. Under the task line, add an indented checklist: - [ ] **N.x** <name> (#<issue>).

Update the parent issue. Add the sub-issue links and the spec reference.

Label lifecycle (for whoever completes a sub-task)

When a blocking sub-task closes, remove its blocked-by-<its-number> label from every issue carrying it, and tick the sub-task checkbox in TODO.md.

divide-task— agent skill

Is divide-task safe to install?

divide-task

Workflow

Label lifecycle (for whoever completes a sub-task)

Audit the pieces. Scan the whole. Decide.