assimilate-popular-workflows

# Assimilate Popular Workflows Search public GitHub repositories for SKILL.md files, classify each repo by archetype, and maintain structured research documents under `docs/reference-repos/[org]/[repo-name]/`. The goal is not to copy skills verbatim but to extract transferable value: processes for the babysitter process library, babysitter marketplace plugin ideas, and implicit procedural knowledge that can be codified into babysitter JS processes. ### Process Library Placement Rules Extracted processes go into the babysitter process library (`library/`). Placement depends on scope: | What it is | Where it goes | Examples | |------------|---------------|---------| | Full generic dev methodology (entire workflow paradigm) | `methodologies/<name>/` | agile, gsd, tdd, scrum, kanban, waterfall | | Common cross-domain pattern (reusable across many specializations) | `specializations/shared/` | audit-pipeline, expert-advisory, progressive-disclosure | | Domain-specific process | `specializations/<domain>/` | security-compliance, devops-sre-platform, data-science-ml | **Important**: Do NOT place domain-specific processes in `methodologies/`. Only full, generic development methodologies belong there. A "k8s security audit" is `specializations/security-compliance/`, not a methodology. A "deep research pipeline" is `specializations/shared/` (cross-domain). A "TDD agent workflow" is `methodologies/atdd-tdd/` (full dev methodology). ### Plugin Ideas = Babysitter Marketplace Plugins A babysitter plugin is a set of natural language instructions (markdown) or deterministic coded processes (JS) that an AI agent reads and executes to install a modular set of capabilities. A plugin contains at minimum `install.md` with instructions the AI agent follows to modify the user's project. See `docs/plugins.md` for the full specification. **CRITICAL DISTINCTION**: Plugin ideas should ONLY be things that modify project setup, install external integrations, or enforce workflows beyond just adding processes. Do NOT suggest plugins for: - **Skill pack collections**: If you mark processes for extraction, don't suggest a plugin that just bundles those processes - **Expert/Role plugins**: ".NET Expert", "React Native Expert", "Vue Development Suite", "Security Expert" - these are just skill packs - **Domain suites**: "Frontend Development Suite", "DevOps Toolkit", "Data Science Suite" - these bundle processes - **Orchestration patterns**: Multi-agent coordination, session continuity, workflow orchestration belong in babysitter core or as processes - **Process repackaging**: Any plugin that just wraps processes you already marked for extraction Valid plugin ideas change the project or setup (may not install skills at all): - **Project configuration changes**: Modify CLAUDE.md/AGENTS.md instructions, update settings, configure behaviors - **External service integrations**: GitHub API, Slack API, database connections, CLI tools, MCP servers - **Project enforcement mechanisms**: Git hooks, ESLint rules, pre-commit checks, CI/CD pipeline templates - **Infrastructure and deployment**: Docker configs, cloud provider setup, deployment templates, containerization - **Memory and persistence systems**: Context storage, session state, cross-run memory, caching layers - **Development environment changes**: IDE integrations, build tool configs, linting setups, editor extensions - **Workflow enforcement**: Harness hooks, commit policies, pipeline triggers, quality gates, approval workflows - **Project structure modifications**: Directory layouts, file templates, scaffolding, boilerplate generation - **Additional project functionality**: New capabilities, tool chains, automation layers, monitoring integration **Rule of thumb**: If it teaches babysitter how to do something → process. If it changes the project, adds external connections, or modifies behavior → plugin. **Valid plugin use case categories** (derived from the existing marketplace): | Category | What the plugin installs | Examples | |----------|-------------------------|----------| | Security & Sandboxing | Lint rules, git hooks, scanning processes, sandboxing policies | basic-security, agentsh | | Context & Memory | MCP servers for memory, lifecycle hooks for auto-capture | claude-mem, mempalace | | Knowledge Management | Wiki systems, knowledge graphs, semantic search engines | llm-wiki, graphify, qmd | | Developer Experience & UX | Status indicators, session landing pages, skill recommenders | ctx, status-line, welcome | | Tools Integration | Browser automation, external tool integration, MCP tools for new capabilities | dev-browser, prompt-master | | CI/CD Integration | GitHub Actions workflows, harness-specific pipeline templates | github-actions-cicd-* | | DevOps & Infrastructure | IaC templates, deployment configs, cloud provider setup | project-deployment | | Quality Assurance & Testing | Test frameworks, coverage gates, linting configs, pre-commit hooks | testing-suite | | Workflow Automation | Rate limit handling, auto-retry logic, lifecycle event hooks | rate-limit-handler | | Theming & Environment | Sound hooks, design systems, conversational personality, themed assets | themes, sound-hooks | | Harness Integration | Alternative harness adapters, TUI improvements, orchestration frameworks | opencode-adapter, workflow-orchestration | **IMPORTANT DISTINCTION**: Do NOT confuse babysitter marketplace plugins with harness assimilation: - **Babysitter marketplace plugins**: Install INTO user projects via `install.md` to add capabilities - **Harness assimilation**: Create plugins FOR other harnesses (like hermes-agent) that integrate babysitter INTO those harnesses ## When to use - User asks to discover what skills or workflows exist in popular repos. - User asks to research a specific repo's skill ecosystem. - User asks to extract processes or patterns from external skills. - Periodic refresh to track the evolving skill landscape. ## Phase 1 -- Discovery Search GitHub for repositories containing SKILL.md files. Use multiple search strategies to cast a wide net: ```bash # Primary: find SKILL.md files in public repos gh search code "filename:SKILL.md" --json repository,path,url --limit 100 # Supplementary: search for skill frontmatter patterns gh search code "description:" "filename:SKILL.md" --json repository,path,url --limit 100 # Claude Code plugin skills specifically gh search code "plugin.json" "skills" --json repository,path,url --limit 100 ``` ### Topic-based discovery Search for repos tagged with relevant GitHub topics. These are high-signal candidates even without SKILL.md files: ```bash # Search by topic tags (each is a separate query) for topic in claude-code claude-skills mcp agentic-workflow agent-skills skills agent-harness ai-agents; do gh search repos --topic "$topic" --stars=">50" --sort stars --limit 50 --json fullName,stargazersCount,description done # Combined keyword + star searches for broader coverage gh search repos "agent skill" --stars=">50" --sort stars --limit 50 --json fullName,stargazersCount,description gh search repos "claude code skills" --stars=">100" --sort stars --limit 30 --json fullName,stargazersCount,description gh search repos "workflow automation skill" --stars=">100" --sort stars --limit 30 --json fullName,stargazersCount,description ``` Topic-tagged repos that lack SKILL.md files may still contain extractable processes or plugin ideas if they implement multi-step workflows, domain pipelines, or tool integrations. Classify and research them using the same Phase 2/3 pipeline. ### Marketplace/registry discovery Browse public skill and plugin registries for high-download or featured entries. These surface popular repos that may not appear in GitHub search: - **ClawHub Skills**: https://clawhub.ai/skills?sort=downloads -- browse top skills by download count. Each skill links to a GitHub repo. Extract repo URLs and cross-reference with the tracked set. - **ClawHub Plugins**: https://clawhub.ai/plugins -- browse plugins by popularity. Each plugin links to a GitHub repo. Extract repo URLs and cross-reference. Use a browser tool or `curl` to fetch these pages and extract GitHub repo links. For each new repo found, enrich and classify using the standard pipeline. ### Filtering rules 1. Drop any hit from `a5c-ai/babysitter` (this repo). 2. **Handle archived/moved repos.** If a repo is archived, check for a successor/migration notice. If the archive points to a new location (e.g., "moved to org/new-repo"), skip the archived repo and evaluate the new location instead. Only track active, maintained repositories. 3. **Drop repos without a permissive license.** Only track repos with MIT, BSD (2-clause or 3-clause), or Apache-2.0 licenses. Drop repos with GPL, AGPL, CC-NC, CC-SA, proprietary, or no license specified. Check `license.spdx_id` during enrichment. 4. Dedupe by `repository.nameWithOwner`. 5. Group hits by repo -- one repo may contain many SKILL.md files. 6. **Prefer repos with 50+ stars.** Lower-star repos may be included only if they contain exceptionally novel processes not found elsewhere. Use `gh search repos` with `--stars=">50"` to find higher-quality repos. ### Enrichment For each surviving repo: ```bash gh api repos/<owner>/<name> \ --jq '{nameWithOwner, description, stargazerCount: .stargazers_count, pushedAt: .pushed_at, topics, license: .license.spdx_id}' ``` Record the list of SKILL.md paths found per repo. ## Phase 2 -- Classification For each repo, shallow-clone into `.a5c/tmp/skill-discovery/` and investigate the structure. Classify into exactly one archetype: | Archetype | Description | Action | |-----------|-------------|--------| | `mega-skill-pack` | Repo exists to distribute many skills across domains | Deep-dive: catalog all skills, extract patterns | | `methodology-repo` | Repo represents a specific workflow or methodology | Extract the methodology as a potential babysitter process | | `internal-maintenance` | Skills exist only for the repo's own CI/dev workflow | **Skip** -- not transferable | | `other-harness` | Skill is specific to a non-Claude harness (Codex, Cursor, etc.) or focused on harness invocation/CLI orchestration | **Skip** -- not transferable to babysitter processes | | `claude-plugin` | A Claude Code plugin with skills as part of its offering | Investigate plugin structure, extractable integrations | | `harness-framework` | Alternative AI coding harness/framework (OpenCode, Antigravity, etc.) or Claude Code orchestration/TUI improvements | Extract for harness assimilation (new adapter + plugin) and/or TUI/orchestration improvements | | `domain-skill-pack` | Skills focused on a specific domain (e.g., data science, DevOps) | Extract domain processes and patterns | | `utility-with-skill` | A tool/library that ships a SKILL.md for usage guidance | Extract the usage pattern as a potential shared process | | `not-a-skill` | Repo uses SKILL.md as generic docs, no Claude Code connection | **Skip** -- no frontmatter, no agent context | ### Classification signals Read the repo's top-level README, plugin.json (if present), directory structure, and a sample of SKILL.md files. Look for: - **mega-skill-pack**: `skills/` directory with 5+ subdirectories, no primary application code - **methodology-repo**: Process/workflow documentation dominates, SKILL.md describes a methodology - **internal-maintenance**: SKILL.md references only internal paths, CI pipelines, repo-specific tooling - **other-harness**: Skill is for Codex, Cursor, or another non-Claude harness; or focuses on CLI orchestration / harness invocation patterns - **claude-plugin**: `.claude-plugin/plugin.json` or `plugin.json` with skill registrations - **harness-framework**: CLI executable for AI interaction (like `opencode`, `antigravity`), or Claude Code orchestration/TUI/hook improvements (workflow automation, delegation frameworks, status line enhancements) - **domain-skill-pack**: Skills all relate to one domain; directory structure groups by topic - **utility-with-skill**: Repo is primarily a library/tool; SKILL.md is usage documentation ## Phase 3 -- Deep Research For each non-skipped repo, produce a single `research.md` file containing overview, assessment, and extractable value. **Harness Capability Verification**: For repos classified as `harness-framework`, verify three critical capabilities for babysitter integration: 1. **Custom Tools/MCP**: Can execute custom tools, MCP servers, or bash commands 2. **Stop Hooks**: Has stop-hooks or end-turn hooks to interrupt agent conversation for feedback 3. **Plugin System**: Plugin/extension system with manifests and optionally marketplace Use WebSearch/WebFetch to research the harness documentation and verify these capabilities. Stop hooks are CRITICAL - without them, babysitter's orchestration loop cannot function (harness must be interruptible between iterations for feedback). ### Directory layout - **GitHub-sourced repos**: `docs/reference-repos/[org]/[repo-name]/research.md` - **ClawHub-sourced skills/plugins**: `docs/reference-repos/clawhub/[author]/[skill-name]/research.md` Each tracked repo gets exactly **one file** (`research.md`) in its directory. Do not split into multiple files (no separate `index.md` or `extractable-value.md`). ### `research.md` -- Unified research document ```markdown # [org]/[repo-name] - **Archetype**: mega-skill-pack | methodology-repo | claude-plugin | domain-skill-pack | utility-with-skill - **Stars**: N - **Last pushed**: YYYY-MM-DD - **License**: MIT / Apache-2.0 / BSD-2-Clause / BSD-3-Clause - **Discovered**: YYYY-MM-DD - **Source**: gh-search | clawhub-skills | clawhub-plugins | topic:X - **Skills found**: N ## Summary <2-3 sentences on what the repo provides and why it's interesting> ## Assessment <What is transferable? What is repo-specific? Quality of skill design? Look beyond methodologies -- domain-specific skills (DevOps, security, frontend, data, etc.) often contain multi-step processes extractable as specializations/<domain>/ entries. A "kubernetes-specialist" skill may encode a k8s deployment audit process. A "debugging-wizard" may encode a systematic debugging process. For harness-framework repos, assess: TUI/orchestration improvements for our internal agent harness, CLI patterns for new harness adapter creation, and workflow automation patterns. Assess each skill for procedural content, not just methodology content.> ## Extraction Priority - High / Medium / Low - Rationale: <why> ## Skills Inventory | Skill | Path | Domain | Transferable? | Notes | |-------|------|--------|---------------|-------| | skill-name | skills/foo/SKILL.md | DevOps | Yes - pattern | Describes a CI/CD workflow | ## Processes <Workflows that can be codified as babysitter JS processes. Domain-specific skills are prime extraction targets -- a "react-expert" skill may contain a component architecture review process (specializations/frontend/), a "terraform-engineer" may contain an IaC audit process (specializations/devops-sre-platform/), etc. Don't dismiss domain skills as "just expert personas" -- read them for procedural content.> - **Process name**: Description of what it does - Source: path/to/SKILL.md (lines N-M) - Placement: methodologies/<name> | specializations/shared | specializations/<domain> - Inputs/Outputs: ... - Complexity: simple | moderate | complex - Notes: ... ## Plugin Ideas <Ideas for babysitter marketplace plugins -- installable packages with install.md that an AI agent executes to set up capabilities in a user's project> - **Plugin name**: What it installs and configures - What install.md would do: <what the AI agent does during install -- detect stack, interview user, copy processes, set up hooks/configs> - Processes it would copy: <which process library entries> - Configs/hooks it would create: <ESLint rules, git hooks, CI/CD templates, etc.> - Source evidence: <what in the repo inspires this plugin idea> - Marketplace placement: <plugins/a5c/marketplace/blueprints/[category]/[plugin-name]/> ## Plugin Marketplace Mapping <Check existing marketplace plugins before proposing new ones. Map plugin ideas against current plugins/a5c/marketplace/blueprints/ structure> | Plugin Idea | Marketplace Status | Action | Existing Plugin | Target Placement | |-------------|-------------------|--------|-----------------|------------------|