domains / families / software-engineering / conductor-validator

conductor-validator

combined

Validates Conductor project artifacts for completeness, 'Validates Conductor project artifacts for completeness,

When to use

• Working on check if conductor directory exists tasks or workflows
• Needing guidance, best practices, or checklists for check if conductor directory exists
• Inspect a project that actually uses a `conductor/` workflow directory after setup, before resuming a track, or when diagnosing inconsistent plans/status. This is distinct from the Rails Conductor desktop-app setup (`conductor.json`/`scrip…

When not to use

• The task is unrelated to check if conductor directory exists
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first copy (rmyndharis) is a thin wrapper that provides discovery commands and pattern matching but lacks a substantive validation procedure, relying on generic instructions. The second copy (sickn33) provides a detailed, 5-step validation procedure (comparing declared vs. actual files, resolving links, reconciling state) and explicit safety constraints (read-only, do not create missing paths). The second copy is a more complete implementation of the skill's intent, but the first copy's specific bash discovery commands are slightly different (using `ls -la` vs `ls -ld` and checking for existence vs listing). More importantly, the second copy explicitly states it is distinct from Rails Conductor setup, a constraint the first lacks. Combining them ensures the agent has both the specific discovery commands and the rigorous validation logic.