Skip to content

aiskillstore/marketplace / skills/89jobrien/use-conductor

use-conductor

Verified

Scan conductor/ directory for project direction, workflows, and task planning when present

FileKindSize
SKILL.mdskill md3.2 KB
skill-report.jsonconfig27.1 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-05T14:16:24.699Z",
    "slug": "89jobrien-use-conductor",
    "source_url": "https://github.com/89jobrien/steve/tree/main/steve/skills/use-conductor",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "44ff45b485c715403588ac37f737593e7e32a297081bb0742f71ba07fbd54531",
    "tree_hash": "190a6ebe80cdaa90607c299f0b6685c01aba3e1c7f29ccb2b9ffaec854948af1",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "use-conductor",
    "description": "Use conductor files to find project context, active tracks, workflow rules, and the next planned task.",
    "summary": "Read conductor project files before starting work.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "89jobrien",
    "license": "MIT",
    "category": "productivity",
    "tags": [
      "project-planning",
      "workflow",
      "task-management",
      "repository-context",
      "agent-guidance"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands"
    ]
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "All static command-execution detections are markdown backticks, code fences, file names, or checklist markers in SKILL.md. I found no command execution, network calls, prompt injection, or reconnaissance intent. The blocker finding on line 69 is a false match on the `[~]` task status marker.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 8,
            "line_end": 8
          },
          {
            "file": "SKILL.md",
            "line_start": 24,
            "line_end": 40
          },
          {
            "file": "SKILL.md",
            "line_start": 40,
            "line_end": 46
          },
          {
            "file": "SKILL.md",
            "line_start": 46,
            "line_end": 47
          },
          {
            "file": "SKILL.md",
            "line_start": 47,
            "line_end": 48
          },
          {
            "file": "SKILL.md",
            "line_start": 48,
            "line_end": 49
          },
          {
            "file": "SKILL.md",
            "line_start": 49,
            "line_end": 50
          },
          {
            "file": "SKILL.md",
            "line_start": 50,
            "line_end": 51
          },
          {
            "file": "SKILL.md",
            "line_start": 51,
            "line_end": 51
          },
          {
            "file": "SKILL.md",
            "line_start": 52,
            "line_end": 56
          },
          {
            "file": "SKILL.md",
            "line_start": 56,
            "line_end": 58
          },
          {
            "file": "SKILL.md",
            "line_start": 58,
            "line_end": 59
          },
          {
            "file": "SKILL.md",
            "line_start": 59,
            "line_end": 60
          },
          {
            "file": "SKILL.md",
            "line_start": 60,
            "line_end": 61
          },
          {
            "file": "SKILL.md",
            "line_start": 61,
            "line_end": 61
          },
          {
            "file": "SKILL.md",
            "line_start": 62,
            "line_end": 66
          },
          {
            "file": "SKILL.md",
            "line_start": 66,
            "line_end": 68
          },
          {
            "file": "SKILL.md",
            "line_start": 68,
            "line_end": 69
          },
          {
            "file": "SKILL.md",
            "line_start": 69,
            "line_end": 70
          },
          {
            "file": "SKILL.md",
            "line_start": 70,
            "line_end": 76
          },
          {
            "file": "SKILL.md",
            "line_start": 76,
            "line_end": 77
          },
          {
            "file": "SKILL.md",
            "line_start": 77,
            "line_end": 77
          },
          {
            "file": "SKILL.md",
            "line_start": 79,
            "line_end": 80
          },
          {
            "file": "SKILL.md",
            "line_start": 80,
            "line_end": 86
          },
          {
            "file": "SKILL.md",
            "line_start": 86,
            "line_end": 93
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:SKILL.md:8:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 8,
        "line_end": 8,
        "snippet": "Scan the `conductor/` directory at project root for structured project management files that provide"
      },
      {
        "id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 24,
        "line_end": 40,
        "snippet": "```text"
      },
      {
        "id": "external_commands:SKILL.md:40:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 40,
        "line_end": 46,
        "snippet": "```"
      },
      {
        "id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 46,
        "line_end": 47,
        "snippet": "| `product.md` | Product vision, target audience, core features |"
      },
      {
        "id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 47,
        "line_end": 48,
        "snippet": "| `product-guidelines.md` | Naming conventions, quality standards, documentation rules |"
      },
      {
        "id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 48,
        "line_end": 49,
        "snippet": "| `tech-stack.md` | Approved technologies and libraries |"
      },
      {
        "id": "external_commands:SKILL.md:49:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 49,
        "line_end": 50,
        "snippet": "| `workflow.md` | TDD methodology, task workflow, commit guidelines |"
      },
      {
        "id": "external_commands:SKILL.md:50:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 50,
        "line_end": 51,
        "snippet": "| `tracks.md` | High-level index of all work tracks |"
      },
      {
        "id": "external_commands:SKILL.md:51:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 51,
        "line_end": 51,
        "snippet": "| `tracks/<name>/plan.md` | Detailed task checklist with `[ ]`, `[~]`, `[x]` status |"
      },
      {
        "id": "external_commands:SKILL.md:52:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 52,
        "line_end": 56,
        "snippet": "| `tracks/<name>/spec.md` | Goals, scope, and success criteria for the track |"
      },
      {
        "id": "external_commands:SKILL.md:56:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 56,
        "line_end": 58,
        "snippet": "1. Check if `conductor/` directory exists at project root"
      },
      {
        "id": "external_commands:SKILL.md:58:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 58,
        "line_end": 59,
        "snippet": "- `product.md` for vision"
      },
      {
        "id": "external_commands:SKILL.md:59:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 59,
        "line_end": 60,
        "snippet": "- `product-guidelines.md` for standards"
      },
      {
        "id": "external_commands:SKILL.md:60:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 60,
        "line_end": 61,
        "snippet": "- `tracks.md` for active work"
      },
      {
        "id": "external_commands:SKILL.md:61:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 61,
        "line_end": 61,
        "snippet": "3. For active tracks (marked `[~]`), read the track's `plan.md` to find current tasks"
      },
      {
        "id": "external_commands:SKILL.md:62:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 62,
        "line_end": 66,
        "snippet": "4. Follow the workflow methodology defined in `workflow.md`"
      },
      {
        "id": "external_commands:SKILL.md:66:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 66,
        "line_end": 68,
        "snippet": "In `plan.md` files:"
      },
      {
        "id": "external_commands:SKILL.md:68:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 68,
        "line_end": 69,
        "snippet": "- `[ ]` - Task not started"
      },
      {
        "id": "external_commands:SKILL.md:69:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 69,
        "line_end": 70,
        "snippet": "- `[~]` - Task in progress"
      },
      {
        "id": "external_commands:SKILL.md:70:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 70,
        "line_end": 76,
        "snippet": "- `[x]` - Task completed (may include commit SHA)"
      },
      {
        "id": "external_commands:SKILL.md:76:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 76,
        "line_end": 77,
        "snippet": "1. **Respect the plan** - Follow the task order in `plan.md`"
      },
      {
        "id": "external_commands:SKILL.md:77:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 77,
        "line_end": 77,
        "snippet": "2. **Update status** - Mark tasks as `[~]` when starting, `[x]` when done"
      },
      {
        "id": "external_commands:SKILL.md:79:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 79,
        "line_end": 80,
        "snippet": "4. **Maintain standards** - Follow `product-guidelines.md` and style guides"
      },
      {
        "id": "external_commands:SKILL.md:80:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 80,
        "line_end": 86,
        "snippet": "5. **Stay in scope** - Check `spec.md` for what's in/out of scope"
      },
      {
        "id": "external_commands:SKILL.md:86:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 86,
        "line_end": 93,
        "snippet": "```text"
      },
      {
        "id": "blocker:SKILL.md:69:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "SKILL.md",
        "line_start": 69,
        "line_end": 70,
        "snippet": "- `[~]` - Task in progress"
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:SKILL.md:8:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.98,
        "reason": "Line 8 uses inline markdown backticks around a directory name in descriptive prose. It does not invoke a shell or evaluate Ruby backticks."
      },
      {
        "id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.98,
        "reason": "Line 24 opens a fenced text block that documents a directory layout. It is static markdown documentation, not executable shell or Ruby code."
      },
      {
        "id": "external_commands:SKILL.md:40:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.98,
        "reason": "Line 40 closes the fenced text block. A markdown fence is not command execution and has no runtime behavior."
      },
      {
        "id": "external_commands:SKILL.md:46:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 46 names product.md in a markdown table. The inline backticks format a filename and do not execute a command."
      },
      {
        "id": "external_commands:SKILL.md:47:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 47 uses inline backticks to format product-guidelines.md as a filename. There is no shell command or dynamic execution."
      },
      {
        "id": "external_commands:SKILL.md:48:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 48 lists tech-stack.md as documentation. The backticks are markdown formatting, not a Ruby shell execution construct."
      },
      {
        "id": "external_commands:SKILL.md:49:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 49 lists workflow.md in a file-purpose table. It does not include executable code or user-controlled command input."
      },
      {
        "id": "external_commands:SKILL.md:50:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 50 formats tracks.md as a filename in markdown. The skill text does not run an external command."
      },
      {
        "id": "external_commands:SKILL.md:51:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 51 documents a plan.md path and task markers. The backticks are filename formatting, not command execution."
      },
      {
        "id": "external_commands:SKILL.md:52:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 52 documents a spec.md path in a markdown table. It contains no shell invocation or Ruby backtick evaluation."
      },
      {
        "id": "external_commands:SKILL.md:56:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.94,
        "reason": "Line 56 instructs the agent to check for a conductor directory. It describes normal project-file inspection and does not execute an external command."
      },
      {
        "id": "external_commands:SKILL.md:58:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 58 references product.md as a file to read for context. The inline markdown backticks do not create command execution."
      },
      {
        "id": "external_commands:SKILL.md:59:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 59 references product-guidelines.md as documentation. It is a filename mention, not an executable instruction."
      },
      {
        "id": "external_commands:SKILL.md:60:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 60 references tracks.md for active work context. The backticks are markdown formatting only."
      },
      {
        "id": "external_commands:SKILL.md:61:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "Line 61 describes `[~]` task markers and plan.md files. It contains no shell syntax or dynamic code execution."
      },
      {
        "id": "external_commands:SKILL.md:62:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 62 references workflow.md as project documentation. The text does not invoke an external process."
      },
      {
        "id": "external_commands:SKILL.md:66:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 66 uses inline backticks around plan.md in explanatory text. This is markdown formatting, not execution."
      },
      {
        "id": "external_commands:SKILL.md:68:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 68 formats the `[ ]` status marker in markdown. It is a checklist convention, not a command."
      },
      {
        "id": "external_commands:SKILL.md:69:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 69 formats the `[~]` status marker in markdown. It is only a task-status convention and cannot execute code."
      },
      {
        "id": "external_commands:SKILL.md:70:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "Line 70 describes the `[x]` completion marker and optional commit SHA text. It does not include a shell command."
      },
      {
        "id": "external_commands:SKILL.md:76:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 76 references plan.md as a planning file. The inline backticks are documentation formatting, not executable syntax."
      },
      {
        "id": "external_commands:SKILL.md:77:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.96,
        "reason": "Line 77 tells the agent to update markdown task markers. It edits documentation state and does not run external commands."
      },
      {
        "id": "external_commands:SKILL.md:79:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 79 references product-guidelines.md as a standards file. There is no command invocation or dynamic evaluation."
      },
      {
        "id": "external_commands:SKILL.md:80:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.97,
        "reason": "Line 80 references spec.md in guidance about project scope. The backticks format a filename and do not execute code."
      },
      {
        "id": "external_commands:SKILL.md:86:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.98,
        "reason": "Line 86 opens a fenced text example for skill usage. The fence is markdown documentation and has no execution behavior."
      },
      {
        "id": "blocker:SKILL.md:69:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.99,
        "reason": "Line 69 contains the `[~]` in-progress task marker. There is no network scanning, host discovery, or reconnaissance instruction."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 94,
    "audit_model": "codex",
    "audited_at": "2026-07-05T14:16:24.699Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Scan Conductor Project Plans",
    "value_statement": "Project context is often scattered across planning files. This skill guides Claude, Codex, and Claude Code to read conductor files before work begins.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "conductor directory",
      "project planning",
      "task management",
      "repository context",
      "workflow guidance",
      "agent instructions",
      "development workflow"
    ],
    "actual_capabilities": [
      "Checks whether a conductor directory exists at the project root.",
      "Reads core conductor files for product direction, standards, and active work.",
      "Identifies active tracks marked with the in-progress status marker.",
      "Finds current tasks from track plan files.",
      "Applies workflow guidance from conductor workflow documentation.",
      "Uses conductor status markers when updating task progress."
    ],
    "limitations": [
      "Works only when a project includes conductor files.",
      "Depends on the accuracy of the project planning documents.",
      "Does not create a project plan unless the user asks.",
      "Does not replace direct user instructions or repository policies."
    ],
    "use_cases": [
      {
        "title": "Find the next planned task",
        "description": "Read active conductor tracks and identify the next unchecked task before starting implementation.",
        "target_user": "Software developer"
      },
      {
        "title": "Follow repository workflow rules",
        "description": "Load workflow and guideline files so coding work follows the project process.",
        "target_user": "AI coding agent user"
      },
      {
        "title": "Understand project direction quickly",
        "description": "Review product and track documents to summarize project goals and current work.",
        "target_user": "Technical lead"
      }
    ],
    "prompt_templates": [
      {
        "title": "Check for conductor context",
        "prompt": "Check whether this project has conductor files and summarize the key context before making changes.",
        "scenario": "Beginner setup"
      },
      {
        "title": "Find my next task",
        "prompt": "Use the conductor plan to find the active track and tell me the next task to work on.",
        "scenario": "Task selection"
      },
      {
        "title": "Prepare for implementation",
        "prompt": "Read the conductor workflow, active track plan, and relevant guidelines before implementing the selected task.",
        "scenario": "Development planning"
      },
      {
        "title": "Align work with conductor",
        "prompt": "Use conductor files to validate scope, workflow, and task status before editing code for the active track.",
        "scenario": "Advanced project alignment"
      }
    ],
    "output_examples": [
      {
        "input": "What should I work on next?",
        "output": "The active conductor track points to the next unchecked task. The summary includes the track goal, current status, and relevant workflow notes."
      },
      {
        "input": "Start the planned implementation task.",
        "output": "The agent reviews the conductor workflow, marks the task in progress when appropriate, and follows the documented project standards."
      },
      {
        "input": "Summarize the project before making changes.",
        "output": "The response covers product purpose, active tracks, standards, and any workflow rules found in conductor files."
      }
    ],
    "best_practices": [
      "Run the skill before starting work in an unfamiliar repository.",
      "Keep conductor files current so task selection stays accurate.",
      "Confirm the selected task with the user when the plan is ambiguous."
    ],
    "anti_patterns": [
      "Do not assume conductor files exist in every repository.",
      "Do not ignore newer user instructions when conductor files are outdated.",
      "Do not mark tasks complete before verification is finished."
    ],
    "faq": [
      {
        "question": "What is a conductor directory?",
        "answer": "It is a project folder that stores product direction, workflow rules, and track plans."
      },
      {
        "question": "Does this skill execute commands?",
        "answer": "No. It provides instructions for reading planning files and following documented workflow."
      },
      {
        "question": "Which tools can use this skill?",
        "answer": "The report lists support for Claude, Codex, and Claude Code."
      },
      {
        "question": "What happens if conductor files are missing?",
        "answer": "The agent should continue with normal repository discovery and user instructions."
      },
      {
        "question": "Can it update task status?",
        "answer": "Yes, when appropriate. It uses the status markers documented in conductor plan files."
      },
      {
        "question": "Does it replace project documentation?",
        "answer": "No. It depends on project documentation and helps the agent use it consistently."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 94
    }
  ]
}
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall