Is managing-project-releases safe to install?

SaferSkills independently audited managing-project-releases (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/managing-project-releases/SKILL.md · 1 file

.claude/skills/managing-project-releases/SKILL.md2.3 KB · Markdown

name: managing-project-releases

description: Decomposes features or releases into BDD-formatted GitHub issues with Given/When/Then scenarios and test cases. Creates milestones, assigns labels, and adds issues to the project board. Use when starting a new release, planning a feature, or creating issue tickets.

Managing Project Releases

Context

GitHub repo: darkcofy/sqlprism
GitHub Project: SQLPrism (project number 1, owner darkcofy)
Labels: enhancement, bug, chore (no sizing labels)
Branch convention: feat-<name>, fix-<name>, chore-<name>

Workflow

Read the implementation plan for the release from .claude/plans/
Create a milestone named after the release version (e.g., v1.0.1)
Decompose into issues — one per logical unit of work
Write each issue in BDD format — see BDD-TEMPLATE.md
Add all issues to the GitHub Project board
Update dependency references with actual issue numbers after creation

Issue Decomposition Guidelines

Break work into issues that are:

Independent where possible — parallelizable steps get separate issues
Ordered by dependency — identify what blocks what
Testable — every issue has BDD scenarios that become test cases
Single responsibility — one issue = one logical change

Group by layer, not by file. Example layers:

Schema/migration changes
Renderer/parser changes
Core logic (indexer, engine)
API/tool surface (MCP tools, CLI commands)
Tests (can be a single issue or per-layer)

Creating Issues

gh issue create \
  --milestone "<version>" \
  --label "<type>" \
  --title "<concise title>" \
  --body "$(cat <<'EOF'
<BDD body — see BDD-TEMPLATE.md>
EOF
)"

After creating all issues, add them to the project:

gh project item-add 1 --owner darkcofy --url "<issue_url>"

Then update dependency cross-references to use actual issue numbers.

Creating Milestones

gh api repos/darkcofy/sqlprism/milestones \
  -f title="<version>" \
  -f description="<one-line summary>" \
  -f state="open"

Label Selection

Label	When to use
`enhancement`	New features, new capabilities
`bug`	Fixing broken behavior
`chore`	Migrations, CI, deps, refactors

managing-project-releases— agent skill

Is managing-project-releases safe to install?

Managing Project Releases

Context

Workflow

Issue Decomposition Guidelines

Creating Issues

Creating Milestones

Label Selection

Audit the pieces. Scan the whole. Decide.