Agent skill

Process Builder

by a5c-ai in a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices.

MITAuto-check passedFrontend & Design

Install Process Builder

skills CLI
$ npx skills add a5c-ai/babysitter --skill process-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install a5c-ai/babysitter process-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/a5c-ai/babysitter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/process-builder .claude/skills/process-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
process-builder
GitHub stars
1.8k
Used in
1 other repo
Token cost
~4.5k tokens
SKILL.md length
595 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices.

  • Works in 8 steps: Research & Documentation → Identify Processes → Create Process Files → …
  • Tasks that involve Responsive design
  • SKILL.md covers Quick Reference, 3-Phase Workflow, Process File Structure and SDK Context API Reference, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Process Builder is an agent skill from a5c-ai/babysitter. Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Responsive design. The repository describes itself as: Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration. The licence is MIT.

When your agent uses it

  • Tasks that involve Responsive design

Example prompts

  • “/process-builder”

Requirements

  • Node.js

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Research & Documentation
  2. Identify Processes
  3. Create Process Files
  4. Gather Requirements
  5. Research Similar Processes
  6. Check Methodologies Backlog
  7. Create the Process
  8. Validate Structure

What it can do on your machine

Read from SKILL.md and the folder at commit feb68ab. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, bash, markdown and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Process Builder loads about 4.5k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 595 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from a5c-ai/babysitter at commit feb68ab, republished under its MIT licence (© a5c-ai). 595 words, ~4,500 tokens.

Download SKILL.mdSave it as .claude/skills/process-builder/SKILL.md (or your agent's skills folder).
name
process-builder
description
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Process Builder

Create new process definitions for the babysitter event-sourced orchestration framework.

Quick Reference

Processes live in: library/
├── methodologies/          # Reusable development approaches (TDD, BDD, Scrum, etc.)
│   └── [name]/
│       ├── README.md       # Documentation
│       ├── [name].js       # Main process
│       └── examples/       # Sample inputs
│
└── specializations/        # Domain-specific processes
    ├── [category]/         # Engineering specializations (direct children)
    │   └── [process].js
    └── domains/
        └── [domain]/       # Business, Science, Social Sciences
            └── [spec]/
                ├── README.md
                ├── references.md
                ├── processes-backlog.md
                └── [process].js

3-Phase Workflow

Phase 1: Research & Documentation

Create foundational documentation:

bash
# Check existing specializations
ls library/specializations/

# Check methodologies
ls library/methodologies/

Create:

  • README.md - Overview, roles, goals, use cases, common flows
  • references.md - External references, best practices, links to sources
Phase 2: Identify Processes

Create processes-backlog.md with identified processes:

markdown
# Processes Backlog - [Specialization Name]

## Identified Processes

- [ ] **process-name** - Short description of what this process accomplishes
  - Reference: [Link to methodology or standard]
  - Inputs: list key inputs
  - Outputs: list key outputs

- [ ] **another-process** - Description
  ...
Phase 3: Create Process Files

Create .js process files following SDK patterns (see below).


Process File Structure

Every process file follows this pattern:

javascript
/**
 * @process [category]/[process-name]
 * @description Clear description of what the process accomplishes end-to-end
 * @inputs { inputName: type, optionalInput?: type }
 * @outputs { success: boolean, outputName: type, artifacts: array }
 *
 * @graph
 *   domains: [domain:software-engineering]
 *   skillAreas: [skill-area:your-skill-area]
 *   topics: [topic:your-topic]
 *   roles: [role:your-role]
 *   workflows: [workflow:your-workflow]
 *
 * @example
 * const result = await orchestrate('[category]/[process-name]', {
 *   inputName: 'value',
 *   optionalInput: 'optional-value'
 * });
 *
 * @references
 * - Book: "Relevant Book Title" by Author
 * - Article: [Title](https://link)
 * - Standard: ISO/IEEE reference
 */

import { defineTask } from '@a5c-ai/babysitter-sdk';

/**
 * [Process Name] Process
 *
 * Methodology: Brief description of the approach
 *
 * Phases:
 * 1. Phase Name - What happens
 * 2. Phase Name - What happens
 * ...
 *
 * Benefits:
 * - Benefit 1
 * - Benefit 2
 *
 * @param {Object} inputs - Process inputs
 * @param {string} inputs.inputName - Description of input
 * @param {Object} ctx - Process context (see SDK)
 * @returns {Promise<Object>} Process result
 */
export async function process(inputs, ctx) {
  const {
    inputName,
    optionalInput = 'default-value',
    // ... destructure with defaults
  } = inputs;

  const artifacts = [];

  // ============================================================================
  // PHASE 1: [PHASE NAME]
  // ============================================================================

  ctx.log?.('info', 'Starting Phase 1...');

  const phase1Result = await ctx.task(someTask, {
    // task inputs
  });

  artifacts.push(...(phase1Result.artifacts || []));

  // Breakpoint for human review (when needed)
  await ctx.breakpoint({
    question: 'Review the results and approve to continue?',
    title: 'Phase 1 Review',
    context: {
      runId: ctx.runId,
      files: [
        { path: 'artifacts/output.md', format: 'markdown', label: 'Output' }
      ]
    }
  });

  // ============================================================================
  // PHASE 2: [PHASE NAME] - Parallel Execution Example
  // ============================================================================

  const [result1, result2, result3] = await ctx.parallel.all([
    () => ctx.task(task1, { /* args */ }),
    () => ctx.task(task2, { /* args */ }),
    () => ctx.task(task3, { /* args */ })
  ]);

  // ============================================================================
  // PHASE 3: [ITERATION EXAMPLE]
  // ============================================================================

  let iteration = 0;
  let targetMet = false;

  while (!targetMet && iteration < maxIterations) {
    iteration++;

    const iterResult = await ctx.task(iterativeTask, {
      iteration,
      previousResults: /* ... */
    });

    targetMet = iterResult.meetsTarget;

    if (!targetMet && iteration % 3 === 0) {
      // Periodic checkpoint
      await ctx.breakpoint({
        question: `Iteration ${iteration}: Target not met. Continue?`,
        title: 'Progress Checkpoint',
        context: { /* ... */ }
      });
    }
  }

  // ============================================================================
  // COMPLETION
  // ============================================================================

  return {
    success: targetMet,
    iterations: iteration,
    artifacts,
    // ... other outputs matching @outputs
  };
}

// ============================================================================
// TASK DEFINITIONS
// ============================================================================

/**
 * Task: [Task Name]
 * Purpose: What this task accomplishes
 */
const someTask = defineTask({
  name: 'task-name',
  description: 'What this task does',

  // Task definition - executed externally by orchestrator
  // This returns a TaskDef that describes HOW to run the task

  inputs: {
    inputName: { type: 'string', required: true },
    optionalInput: { type: 'number', default: 10 }
  },

  outputs: {
    result: { type: 'object' },
    artifacts: { type: 'array' }
  },

  async run(inputs, taskCtx) {
    const effectId = taskCtx.effectId;

    return {
      kind: 'node',  // or 'agent', 'skill', 'shell', 'breakpoint'
      title: `Task: ${inputs.inputName}`,
      node: {
        entry: 'scripts/task-runner.js',
        args: ['--input', inputs.inputName, '--effect-id', effectId]
      },
      io: {
        inputJsonPath: `tasks/${effectId}/input.json`,
        outputJsonPath: `tasks/${effectId}/result.json`
      },
      labels: ['category', 'subcategory']
    };
  }
});

SDK Context API Reference

The ctx object provides these intrinsics:

MethodPurposeBehavior
ctx.task(taskDef, args, opts?)Execute a taskReturns result or throws typed exception
ctx.breakpoint(payload)Human approval gatePauses until approved via human
ctx.sleepUntil(isoOrEpochMs)Time-based gatePauses until specified time
ctx.parallel.all([...thunks])Parallel executionRuns independent tasks concurrently
ctx.parallel.map(items, fn)Parallel mapMaps items through task function
ctx.now()Deterministic timeReturns current Date (or provided time)
ctx.log?.(level, msg, data?)LoggingOptional logging helper
ctx.runIdRun identifierCurrent run's unique ID
Task Kinds
KindUse CaseExecutor
nodeScripts, builds, testsNode.js process
agentLLM-powered analysis, generationClaude Code agent
skillClaude Code skillsSkill invocation
shellSystem commandsShell execution
breakpointHuman approvalBreakpoints UI/service
sleepTime gatesOrchestrator scheduling
orchestrator_taskInternal orchestrator workSelf-routed

Breakpoint Patterns

Basic Approval Gate
javascript
await ctx.breakpoint({
  question: 'Approve to continue?',
  title: 'Checkpoint',
  context: { runId: ctx.runId }
});
With File References (for UI display)
javascript
await ctx.breakpoint({
  question: 'Review the generated specification. Does it meet requirements?',
  title: 'Specification Review',
  context: {
    runId: ctx.runId,
    files: [
      { path: 'artifacts/spec.md', format: 'markdown', label: 'Specification' },
      { path: 'artifacts/spec.json', format: 'json', label: 'JSON Schema' },
      { path: 'src/implementation.ts', format: 'code', language: 'typescript', label: 'Implementation' }
    ]
  }
});
Conditional Breakpoint
javascript
if (qualityScore < targetScore) {
  await ctx.breakpoint({
    question: `Quality score ${qualityScore} is below target ${targetScore}. Continue iterating or accept current result?`,
    title: 'Quality Gate',
    context: {
      runId: ctx.runId,
      data: { qualityScore, targetScore, iteration }
    }
  });
}

Common Patterns

Quality Convergence Loop
javascript
let quality = 0;
let iteration = 0;
const targetQuality = inputs.targetQuality || 85;
const maxIterations = inputs.maxIterations || 10;

while (quality < targetQuality && iteration < maxIterations) {
  iteration++;
  ctx.log?.('info', `Iteration ${iteration}/${maxIterations}`);

  // Execute improvement tasks
  const improvement = await ctx.task(improveTask, { iteration });

  // Score quality (parallel checks)
  const [coverage, lint, security, tests] = await ctx.parallel.all([
    () => ctx.task(coverageTask, {}),
    () => ctx.task(lintTask, {}),
    () => ctx.task(securityTask, {}),
    () => ctx.task(runTestsTask, {})
  ]);

  // Agent scores overall quality
  const score = await ctx.task(agentScoringTask, {
    coverage, lint, security, tests, iteration
  });

  quality = score.overall;
  ctx.log?.('info', `Quality: ${quality}/${targetQuality}`);

  if (quality >= targetQuality) {
    ctx.log?.('info', 'Quality target achieved!');
    break;
  }
}

return {
  success: quality >= targetQuality,
  quality,
  iterations: iteration
};
Phased Workflow with Reviews
javascript
// Phase 1: Research
const research = await ctx.task(researchTask, { topic: inputs.topic });

await ctx.breakpoint({
  question: 'Review research findings before proceeding to planning.',
  title: 'Research Review',
  context: { runId: ctx.runId }
});

// Phase 2: Planning
const plan = await ctx.task(planningTask, { research });

await ctx.breakpoint({
  question: 'Review plan before implementation.',
  title: 'Plan Review',
  context: { runId: ctx.runId }
});

// Phase 3: Implementation
const implementation = await ctx.task(implementTask, { plan });

// Phase 4: Verification
const verification = await ctx.task(verifyTask, { implementation, plan });

await ctx.breakpoint({
  question: 'Final review before completion.',
  title: 'Final Approval',
  context: { runId: ctx.runId }
});

return { success: verification.passed, plan, implementation };
Parallel Fan-out with Aggregation
javascript
// Fan out to multiple parallel analyses
const analyses = await ctx.parallel.map(components, component =>
  ctx.task(analyzeTask, { component }, { label: `analyze:${component.name}` })
);

// Aggregate results
const aggregated = await ctx.task(aggregateTask, { analyses });

return { analyses, summary: aggregated.summary };

Testing Processes

CLI Commands
bash
# Create a new run
babysitter run:create \
  --process-id methodologies/my-process \
  --entry ./library/methodologies/my-process.js#process \
  --inputs ./test-inputs.json \
  --json

# Iterate the run
babysitter run:iterate .a5c/runs/<runId> --json

# List pending tasks
babysitter task:list .a5c/runs/<runId> --pending --json

# Post a task result
babysitter task:post .a5c/runs/<runId> <effectId> \
  --status ok \
  --value ./result.json

# Check run status
babysitter run:status .a5c/runs/<runId>

# View events
babysitter run:events .a5c/runs/<runId> --limit 20 --reverse
Sample Test Input File
json
{
  "feature": "User authentication with JWT",
  "acceptanceCriteria": [
    "Users can register with email and password",
    "Users can login and receive a JWT token",
    "Invalid credentials are rejected"
  ],
  "testFramework": "jest",
  "targetQuality": 85,
  "maxIterations": 5
}

Process Builder Workflow

1. Gather Requirements

Ask the user:

QuestionPurpose
Domain/CategoryDetermines directory location
Process Namekebab-case identifier
GoalWhat should the process accomplish?
InputsWhat data does the process need?
OutputsWhat artifacts/results does it produce?
PhasesWhat are the major steps?
Quality GatesWhere should humans review?
Iteration StrategyFixed phases vs. convergence loop?
2. Research Similar Processes
bash
# Find similar processes
ls library/methodologies/
ls library/specializations/

# Read similar process for patterns
cat library/methodologies/atdd-tdd/atdd-tdd.js | head -200

# Check methodology README structure
cat library/methodologies/atdd-tdd/README.md
3. Check Methodologies Backlog
bash
cat library/methodologies/backlog.md
4. Create the Process

For Methodologies:

  1. Create methodologies/[name]/README.md (comprehensive documentation)
  2. Create methodologies/[name]/[name].js (process implementation)
  3. Create methodologies/[name]/examples/ (sample inputs)

For Specializations:

  1. If domain-specific: specializations/domains/[domain]/[spec]/
  2. If engineering: specializations/[category]/[process].js
  3. Create README.md, references.md, processes-backlog.md first
  4. Then create individual process.js files
Show full SKILL.md (256 more words)Show less
5. Validate Structure

Checklist:

  • JSDoc header with @process, @description, @inputs, @outputs, @example, @references
  • @graph block with relevant atlas node IDs (at minimum one domain)
  • Import from @a5c-ai/babysitter-sdk
  • Main export async function process(inputs, ctx)
  • Input destructuring with defaults
  • Clear phase comments (// === PHASE N: NAME ===)
  • Logging via ctx.log?.('info', message)
  • Tasks via ctx.task(taskDef, inputs)
  • Breakpoints at key decision points
  • Artifact collection throughout
  • Return object matches @outputs schema

Examples by Type

Methodology Process (atdd-tdd style)
javascript
/**
 * @process methodologies/my-methodology
 * @description My development methodology with quality convergence
 * @inputs { feature: string, targetQuality?: number }
 * @outputs { success: boolean, quality: number, artifacts: array }
 */
export async function process(inputs, ctx) {
  const { feature, targetQuality = 85 } = inputs;
  // ... implementation
}
Specialization Process (game-development style)
javascript
/**
 * @process specializations/game-development/core-mechanics-prototyping
 * @description Prototype and validate core gameplay mechanics through iteration
 * @inputs { prototypeName: string, mechanicsToTest: array, engine?: string }
 * @outputs { success: boolean, mechanicsValidated: array, playtestResults: object }
 */
export async function process(inputs, ctx) {
  const { prototypeName, mechanicsToTest, engine = 'Unity' } = inputs;
  // ... implementation
}
Domain Process (science/research style)
javascript
/**
 * @process specializations/domains/science/bioinformatics/sequence-analysis
 * @description Analyze genomic sequences using standard bioinformatics workflows
 * @inputs { sequences: array, analysisType: string, referenceGenome?: string }
 * @outputs { success: boolean, alignments: array, variants: array, report: object }
 */
export async function process(inputs, ctx) {
  const { sequences, analysisType, referenceGenome = 'GRCh38' } = inputs;
  // ... implementation
}

Atlas Graph Metadata

Every generated process file MUST include a @graph JSDoc block in its file header comment alongside the standard @process, @description, @inputs, and @outputs tags.

Format
javascript
/**
 * @process specializations/my-domain/my-process
 * @description ...
 * @inputs { ... }
 * @outputs { ... }
 *
 * @graph
 *   domains: [domain:software-engineering, domain:devops]
 *   skillAreas: [skill-area:caching-strategies]
 *   topics: [topic:microservices, topic:event-sourcing]
 *   roles: [role:backend-engineer, role:sre]
 *   workflows: [workflow:code-review]
 */
How to choose node IDs

Read the atlas graph domain directory (packages/atlas/graph/domain/) to find valid node IDs. The directory contains YAML files grouped by category:

  • domains/ — high-level domain nodes (e.g. domain:software-engineering, domain:devops, domain:data-engineering)
  • skill-areas/ — specific skill area nodes
  • topics/ — granular topic nodes
  • roles/ — role nodes (engineers, practitioners, researchers)
  • workflows/ — workflow nodes

Pick 2–4 edges that genuinely relate to the process. Do not guess IDs — read the actual YAML files to find valid ones. At minimum, every process must reference at least one domain: node.

Why this matters

This metadata connects the process to the atlas knowledge graph. A pre-build generator script parses the @graph block and creates graph nodes and edges for discoverability. Processes without this block will not appear in graph-based search results or recommendations.


Resources

  • SDK Reference: library/reference/sdk.md
  • Methodology Backlog: library/methodologies/backlog.md
  • Specializations Backlog: library/specializations/backlog.md
  • Example: ATDD/TDD: library/methodologies/atdd-tdd/
  • Example: Spec-Driven: library/methodologies/spec-driven-development.js
  • README: Root README.md for full framework documentation

© a5c-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/process-builder of a5c-ai/babysitter.

Open the folder on GitHubat commit feb68ab

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in a5c-ai/babysitter, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Process Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Process Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Process Builder this skilla5c-ai/babysitter1.8k1 repos~4.5kAutomated safety check: PassMIT
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
Material 3hamen/material-3-skill1.5k2 repos~7.8kAutomated safety check: PassMIT
Antislop Layoutmobilemiqdadbadjuber/anti-slop4.6k1 repos~4.1kAutomated safety check: PassMIT
Trip Map Builderhiyeshu/trip-map-builder242—~1.7kAutomated safety check: PassNone
Frontend Design Routercode-yeongyu/oh-my-openagent70k—~5.3kAutomated safety check: PassCustom licence

Similar skills

  • UI Styling

    Ohh-889/skyroc

    Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.

    795 GitHub starsUsed in 13 repos~2.5k tokens
    Frontend & DesignAuto-check passed
  • Material 3

    hamen/material-3-skill

    Implement Google's Material Design 3 (Material You) UI system.

    1.5k GitHub starsUsed in 2 repos~7.8k tokens
    Frontend & DesignAuto-check passed
  • Antislop Layoutmobile

    miqdadbadjuber/anti-slop

    Mobile layout skill for antislop. An agent skill from miqdadbadjuber/anti-slop.

    4.6k GitHub starsUsed in 1 repo~4.1k tokens
    Frontend & DesignAuto-check passed
  • Trip Map Builder

    hiyeshu/trip-map-builder

    End-to-end trip planning: gather user constraints, build a reference itinerary, research locations and dining signals via 大众点评 + 小红书, then generate an interactive mobile-first map page (Leaflet +…

    242 GitHub stars~1.7k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed
  • Frontend Design Router

    code-yeongyu/oh-my-openagent

    Routes frontend and UI work through design reference rulesets, with a design-system gate plus layout and print guidance, before any UI code is written.

    70k GitHub stars~5.3k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Local Testing

    lobehub/lobe-ui

    Local browser verification for the lobe-ui component library and documentation site.

    2.2k GitHub stars~2.1k tokensUpdated today
    Frontend & DesignAuto-check passed

More from a5c-ai/babysitter

All 14 skills in this repo
  • Creates and edits AWS architecture diagrams as DrawIO XML, converting a text description or an image and reading existing files back into shapes.

    1.8k GitHub stars~4.2k tokensUpdated 20 days ago
    Auto-check passed
  • Creates DrawIO XML diagrams of Google Cloud architectures from text or images, and analyzes existing .drawio files to list their GCP components.

    1.8k GitHub stars~3.7k tokensUpdated 20 days ago
    Auto-check passed
  • Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter…

    1.8k GitHub starsUsed in 1 repo~514 tokens
    Auto-check passed
  • Babysitter Process Runner

    a5c-ai/babysitter

    Execute via @babysitter. Use this skill when asked to babysit a task, do anything that is structured process-driven (even a loop) or whenever it is called…

    1.8k GitHub starsUsed in 1 repo~726 tokens
    Auto-check: notes
  • This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns"…

    1.8k GitHub stars~8.5k tokensUpdated 20 days ago
    Auto-check passed
  • Babysit Babysitter Issues

    a5c-ai/babysitter

    This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues…

    1.8k GitHub stars~590 tokensUpdated 20 days ago
    Auto-check passed

Questions about Process Builder

What does Process Builder do?

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Process Builder is an agent skill from a5c-ai/babysitter. Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices.

When should I use Process Builder?

Process Builder fits situations like: tasks that involve Responsive design.

How do I install Process Builder in Claude Code?

Run `npx skills add a5c-ai/babysitter --skill process-builder -a claude-code`. Or copy the skill folder (.claude/skills/process-builder in a5c-ai/babysitter) into .claude/skills/process-builder in your project. Claude Code loads it when a task matches its description.

How do I install Process Builder in Codex?

Run `npx skills add a5c-ai/babysitter --skill process-builder -a codex`. Or copy the skill folder (.claude/skills/process-builder in a5c-ai/babysitter) into .agents/skills/process-builder in your project. Codex loads it when a task matches its description.

Can I use Process Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add a5c-ai/babysitter --skill process-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-builder, .gemini/skills/process-builder, .github/skills/process-builder and .opencode/skills/process-builder in your project.

What does Process Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Process Builder is instructions for the agent only. Our summary lists: Node.js.

Does Process Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Process Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Process Builder use?

Process Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Process Builder use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Process Builder?

Skills that share tags, products or a category with Process Builder: UI Styling (Ohh-889/skyroc, 795 stars), Material 3 (hamen/material-3-skill, 1.5k stars), Antislop Layoutmobile (miqdadbadjuber/anti-slop, 4.6k stars) and Trip Map Builder (hiyeshu/trip-map-builder, 242 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Process Builder?

a5c-ai (a GitHub organization) maintains it in a5c-ai/babysitter, which has 1,833 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 16, 2026.

Source: a5c-ai/babysitter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.