cc-codeconductor 0.2.8 → 0.2.10

package/presets/codex/skills/conductor-setup/SKILL.md

@@ -0,0 +1,125 @@
+---
+name: conductor-setup
+description: Configure a Rails project to work with Conductor (parallel coding agents)
+allowed-tools: Bash(chmod *), Bash(bundle *), Bash(npm *), Bash(script/server)
+context: fork
+risk: unknown
+source: community
+metadata:
+  author: Shpigford
+  version: "1.0"
+---
+
+Set up this Rails project for Conductor, the Mac app for parallel coding agents.
+
+## When to Use
+- You need to configure a Rails project so it runs correctly inside Conductor workspaces.
+- The project should support parallel coding agents with isolated ports, Redis settings, and shared secrets.
+- You want the standard `conductor.json`, `bin/conductor-setup`, and `script/server` scaffolding for a Rails repo.
+
+# What to Create
+
+## 1. conductor.json (project root)
+
+Create `conductor.json` in the project root if it doesn't already exist:
+
+```json
+{
+  "scripts": {
+    "setup": "bin/conductor-setup",
+    "run": "script/server"
+  }
+}
+```
+
+## 2. bin/conductor-setup (executable)
+
+Create `bin/conductor-setup` if it doesn't already exist:
+
+```bash
+#!/bin/bash
+set -e
+
+# Symlink .env from repo root (where secrets live, outside worktrees)
+[ -f "$CONDUCTOR_ROOT_PATH/.env" ] && ln -sf "$CONDUCTOR_ROOT_PATH/.env" .env
+
+# Symlink Rails master key
+[ -f "$CONDUCTOR_ROOT_PATH/config/master.key" ] && ln -sf "$CONDUCTOR_ROOT_PATH/config/master.key" config/master.key
+
+# Install dependencies
+bundle install
+npm install
+```
+
+Make it executable with `chmod +x bin/conductor-setup`.
+
+## 3. script/server (executable)
+
+Create the `script` directory if needed, then create `script/server` if it doesn't already exist:
+
+```bash
+#!/bin/bash
+
+# === Port Configuration ===
+export PORT=${CONDUCTOR_PORT:-3000}
+export VITE_RUBY_PORT=$((PORT + 1000))
+
+# === Redis Isolation ===
+if [ -n "$CONDUCTOR_WORKSPACE_NAME" ]; then
+  HASH=$(printf '%s' "$CONDUCTOR_WORKSPACE_NAME" | cksum | cut -d' ' -f1)
+  REDIS_DB=$((HASH % 16))
+  export REDIS_URL="redis://localhost:6379/${REDIS_DB}"
+fi
+
+exec bin/dev
+```
+
+Make it executable with `chmod +x script/server`.
+
+## 4. Update Rails Config Files
+
+For each of the following files, if they exist and contain Redis configuration, update them to use `ENV.fetch('REDIS_URL', ...)` or `ENV['REDIS_URL']` with a fallback:
+
+### config/initializers/sidekiq.rb
+If this file exists and configures Redis, update it to use:
+```ruby
+redis_url = ENV.fetch('REDIS_URL', 'redis://localhost:6379/0')
+```
+
+### config/cable.yml
+If this file exists, update the development adapter to use:
+```yaml
+development:
+  adapter: redis
+  url: <%= ENV.fetch('REDIS_URL', 'redis://localhost:6379/1') %>
+```
+
+### config/environments/development.rb
+If this file configures Redis for caching, update to use:
+```ruby
+config.cache_store = :redis_cache_store, { url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0') }
+```
+
+### config/initializers/rack_attack.rb
+If this file exists and configures a Redis cache store, update to use:
+```ruby
+Rack::Attack.cache.store = ActiveSupport::Cache::RedisCacheStore.new(url: ENV.fetch('REDIS_URL', 'redis://localhost:6379/0'))
+```
+
+# Implementation Notes
+
+- **Don't overwrite existing files**: Check if conductor.json, bin/conductor-setup, and script/server exist before creating them. If they exist, skip creation and inform the user.
+- **Rails config updates**: Only modify Redis-related configuration. If a file doesn't exist or doesn't use Redis, skip it gracefully.
+- **Create directories as needed**: Create `script/` directory if it doesn't exist.
+
+# Verification
+
+After creating the files:
+1. Confirm all Conductor files exist and scripts are executable
+2. Run `script/server` to verify it starts without errors
+3. Check that Rails configs properly reference `ENV['REDIS_URL']` or `ENV.fetch('REDIS_URL', ...)`
+
+## Limitations
+- 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.

package/presets/codex/skills/find-skills/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Check the Leaderboard First
+
+Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
+
+For example, top skills for web development include:
+- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
+- `anthropics/skills` — Frontend design, document processing (100K+ installs)
+
+### Step 3: Search for Skills
+
+If the leaderboard doesn't cover the user's need, run the find command:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+### Step 4: Verify Quality Before Recommending
+
+**Do not recommend a skill based solely on search results.** Always verify:
+
+1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
+2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
+3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
+
+### Step 5: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install count and source
+3. The install command they can run
+4. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+(185K installs)
+
+To install it:
+npx skills add vercel-labs/agent-skills@react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
+```
+
+### Step 6: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/presets/codex/skills/multi-agent-orchestration/README.md

@@ -0,0 +1,144 @@
+# Multi-Agent Orchestration - Code Structure
+
+This skill uses supporting Python files to keep documentation lean and maintainable.
+
+## Directory Structure
+
+```
+multi-agent-orchestration/
+├── SKILL.md                           # Main documentation (patterns, concepts)
+├── README.md                          # This file
+├── examples/                          # Implementation examples
+│   ├── orchestration_patterns.py      # Sequential, parallel, hierarchical, consensus
+│   └── framework_implementations.py   # CrewAI, AutoGen, LangGraph, Swarm templates
+└── scripts/                           # Utility modules
+    ├── agent_communication.py         # Message broker, shared memory, protocols
+    ├── workflow_management.py         # Workflow execution and optimization
+    └── benchmarking.py                # Performance and collaboration metrics
+```
+
+## Running Examples
+
+### 1. Orchestration Patterns
+```bash
+python examples/orchestration_patterns.py
+```
+Demonstrates sequential, parallel, hierarchical, and consensus orchestration.
+
+### 2. Framework Templates
+```bash
+python examples/framework_implementations.py
+```
+Templates and configurations for CrewAI, AutoGen, LangGraph, and Swarm frameworks.
+
+## Using the Utilities
+
+### Agent Communication
+```python
+from scripts.agent_communication import MessageBroker, SharedMemory, CommunicationProtocol
+
+# Set up communication
+broker = MessageBroker()
+shared_memory = SharedMemory()
+protocol = CommunicationProtocol(broker, shared_memory)
+
+# Send messages between agents
+protocol.request_analysis("agent_a", "agent_b", "Analyze this topic")
+
+# Share findings
+protocol.share_findings("agent_a", "analysis_results", {"findings": "..."})
+
+# Get communication stats
+stats = broker.get_statistics()
+```
+
+### Workflow Management
+```python
+from scripts.workflow_management import WorkflowExecutor, WorkflowOptimizer
+
+# Create and execute workflow
+executor = WorkflowExecutor()
+workflow = executor.create_workflow("workflow_1", "Analysis Workflow")
+
+# Add tasks
+executor.add_task("workflow_1", "task_1", "researcher", "Research the topic")
+executor.add_task("workflow_1", "task_2", "analyst", "Analyze findings", dependencies=["task_1"])
+
+# Execute
+results = executor.execute_workflow("workflow_1", executor_func)
+
+# Analyze workflow
+analysis = WorkflowOptimizer.analyze_dependencies(workflow)
+print(f"Critical path: {analysis['critical_path']}")
+```
+
+### Benchmarking
+```python
+from scripts.benchmarking import TeamBenchmark, AgentEffectiveness, CollaborationMetrics
+
+# Benchmark team performance
+benchmark = TeamBenchmark()
+result = benchmark.run_benchmark("sequential_test", orchestrator, test_data)
+
+# Track agent effectiveness
+effectiveness = AgentEffectiveness()
+effectiveness.record_agent_task("agent_a", "task_1", success=True, quality_score=0.95, duration=2.5)
+
+# Get agent rankings
+rankings = effectiveness.rank_agents()
+for rank, agent, score, metrics in rankings:
+    print(f"{rank}. {agent}: {score:.2f}")
+
+# Analyze collaboration
+collaboration = CollaborationMetrics()
+collaboration.record_interaction("agent_a", "agent_b", "request", response_time=0.5, successful=True)
+interaction_metrics = collaboration.get_interaction_metrics()
+```
+
+## Integration with SKILL.md
+
+- SKILL.md contains conceptual information, orchestration patterns, and best practices
+- Code examples are in `examples/` for clarity and runnable implementations
+- Utilities are in `scripts/` for modular, reusable components
+- This keeps token costs low while maintaining full functionality
+
+## Orchestration Patterns Covered
+
+1. **Sequential Orchestration** - Tasks execute one after another
+2. **Parallel Orchestration** - Multiple agents work simultaneously
+3. **Hierarchical Orchestration** - Manager coordinates specialist teams
+4. **Consensus-Based** - Agents debate and reach consensus
+5. **Adaptive Workflows** - Orchestration changes based on progress
+6. **DAG-Based** - Workflow as directed acyclic graph
+
+## Framework Implementations
+
+- **CrewAI** - Clear roles, hierarchical structure
+- **AutoGen** - Multi-turn conversations, group discussions
+- **LangGraph** - State management, complex workflows
+- **Swarm** - Simple handoffs, conversational workflows
+
+## Key Features
+
+- **Token Efficient**: Modular code structure reduces LLM context usage
+- **Production Ready**: Includes monitoring, optimization, and benchmarking
+- **Framework Agnostic**: Works with any agent framework
+- **Communication Patterns**: Direct, tool-mediated, and manager-based
+- **Performance Metrics**: Team and individual agent effectiveness tracking
+
+## Communication Patterns
+
+- **Direct Communication**: Agent-to-agent message passing
+- **Tool-Mediated**: Agents use shared memory/database
+- **Manager-Based**: Central coordinator manages communication
+- **Broadcast**: One-to-many messaging
+
+## Next Steps
+
+1. Define agent roles and expertise
+2. Choose orchestration pattern (sequential, parallel, hierarchical)
+3. Select communication approach (direct, shared memory, manager)
+4. Implement workflow with task definitions
+5. Set up monitoring and metrics
+6. Benchmark and optimize
+7. Deploy and iterate