rmyndharis/antigravity-skills

conductor-manage

Manage track lifecycle: archive, restore, delete, rename, and cleanup

First seen Jan 23, 2026

Installation

$ npx skills add rmyndharis/antigravity-skills --skill conductor-manage

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rmyndharis/antigravity-skills · top by installs.

npx skills add rmyndharis/antigravity-skills

Browse all from rmyndharis/antigravity-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 1.5K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity
More metadata
argument-hint
[--archive | --restore | --delete | --rename | --list | --cleanup]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,331 B
  • docs SUMMARY.md 93 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 20 installs

SKILL.md

Track Manager

Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts.

Use this skill when

  • Archiving, restoring, renaming, or deleting Conductor tracks
  • Listing track status or cleaning orphaned artifacts
  • Managing the track lifecycle across active, completed, and archived states

Do not use this skill when

  • Conductor is not initialized in the repository
  • You lack permission to modify track metadata or files
  • The task is unrelated to Conductor track management

Instructions

  • Verify conductor/ structure and required files before proceeding.
  • Determine the operation mode from arguments or interactive prompts.
  • Confirm destructive actions (delete/cleanup) before applying.
  • Update tracks.md and metadata consistently.
  • If detailed steps are required, open resources/implementation-playbook.md.

Safety

  • Backup track data before delete operations.
  • Avoid removing archived tracks without explicit approval.

Resources

  • resources/implementation-playbook.md for detailed modes, prompts, and workflows.