Skills conductor-manage
📦

conductor-manage

Content revision r1 High Risk ⚙️ External commands

Manage Conductor Track Lifecycles

Conductor repositories can accumulate stale tracks, archived work, and inconsistent metadata. This skill guides Claude, Codex, and Claude Code through track lifecycle operations.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "conductor-manage" from https://skillstore.io/skills/sickn33-conductor-manage.md and its manifest at https://skillstore.io/api/skills/sickn33-conductor-manage/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-conductor-manage.md Signed manifest GET /api/skills/sickn33-conductor-manage/manifest Signed lockfile GET /api/skills/sickn33-conductor-manage/lockfile

Test it

Using "conductor-manage". List every Conductor track before a planning meeting.

Expected outcome:

  • A grouped overview of active, completed, and archived tracks.
  • Progress counts, recent update dates, and archive readiness notes.

Using "conductor-manage". Archive completed tracks after a release.

Expected outcome:

  • A confirmation screen listing the tracks selected for archive.
  • A completion summary showing moved tracks, updated metadata, and the recorded commit.

Using "conductor-manage". Clean up orphaned track artifacts.

Expected outcome:

  • A categorized issue list for orphaned directories, missing registry entries, incomplete tracks, and stale work.
  • Recommended fixes that wait for approval before modifying repository files.

Security Audit

High Risk
v4 • 7/6/2026 Open versioned report

The static findings are false positives caused by Markdown examples, inline path formatting, and ordinary error text. Semantic review found one real risk in the delete workflow because a track-id placeholder is used directly in destructive remove commands without explicit path normalization. No prompt injection or data exfiltration intent was found.

2
Files scanned
1,161
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

High
resources/implementation-playbook.md:581-588resources/implementation-playbook.md:658-665
Unsafe Destructive Track Deletion
The delete flow accepts a track-id argument and later uses that placeholder in recursive remove commands. Without explicit path normalization and ID validation, a malformed ID could delete files outside the intended Conductor track directory.
The playbook clearly combines user-supplied track IDs with rm -rf paths. Existing confirmation steps reduce accidental deletion, but they do not prove path confinement.

Risk Factors

⚙️ External commands (4)
SKILL.md:26 SKILL.md:29 SKILL.md:30 SKILL.md:39
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-conductor-manage/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-conductor-manage/security.svg)](https://skillstore.io/skills/sickn33-conductor-manage?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-conductor-manage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-conductor-manage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-conductor-manage.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). conductor-manage security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-conductor-manage/audits/4

BibTeX citation

@techreport{sickn33-sickn33-conductor-manage-2026, author = {sickn33}, title = {conductor-manage security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-conductor-manage/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "conductor-manage security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-06" url: "https://skillstore.io/skills/sickn33-conductor-manage/audits/4" identifiers: - type: other value: "skillstore:sickn33-conductor-manage:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Archive Completed Delivery Work

Move finished Conductor tracks into the archive while keeping registry metadata consistent.

Restore Prior Planning Context

Bring an archived track back into active work when a feature or fix resumes.

Clean Project Tracking Drift

Review orphaned folders, missing metadata, and stale in-progress tracks before release planning.

Try These Prompts

List Track Status 
Use conductor-manage to list all Conductor tracks and summarize active, completed, and archived work.
Archive Completed Tracks 
Use conductor-manage to find completed tracks that can be archived. Ask for confirmation before changing files.
Restore Or Rename A Track 
Use conductor-manage to restore an archived track or rename a track ID. Validate conflicts before applying changes.
Audit And Cleanup Drift 
Use conductor-manage cleanup mode to identify orphaned artifacts, incomplete tracks, and stale work. Propose fixes before editing.

Best Practices

  • Run list mode first so track state is clear before making changes.
  • Back up important track data before delete or cleanup operations.
  • Review generated changes in tracks.md and metadata before committing.

Avoid

  • Do not use delete mode when archive mode would preserve useful context.
  • Do not run cleanup fixes without reading the issue list first.
  • Do not rename tracks without checking for references in related documentation.

Frequently Asked Questions

What does this skill manage?
It manages Conductor tracks, including listing, archive, restore, rename, delete, and cleanup workflows.
Can it work outside a Conductor repository?
No. It expects conductor/product.md, conductor/tracks.md, and conductor/tracks/ to exist.
Does delete mode require confirmation?
Yes. The playbook requires explicit confirmation and warns when a track is in progress.
Can archived tracks be restored?
Yes. The restore flow checks for conflicts, moves the track back, and updates registry metadata.
Does rename mode update git history?
No. It updates current track files and metadata, but historical commits keep their original references.
Which assistants can use it?
The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/conductor-manage

Ref

6425ec35f4ac137735cff58cd7877843bba23e3b

Maintenance freshness

7/18/2026

Usage

7 downloads · 88 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all