Agent skill

Agent Production Validator

by ruvnet in ruvnet/ruflo

Agent skill for production-validator - invoke with $agent-production-validator

MITAuto-check passed

Install Agent Production Validator

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-production-validator -a claude-code

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

GitHub CLI
$ gh skill install ruvnet/ruflo agent-production-validator --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/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-production-validator .claude/skills/agent-production-validator && 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
agent-production-validator
GitHub stars
74k
Used in
2 other repos
Token cost
~3k tokens
SKILL.md length
325 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Agent skill for production-validator - invoke with $agent-production-validator

  • Works in 12 steps: Implementation Completeness Check → Real Database Integration → External API Integration → …
  • SKILL.md covers Core Responsibilities, Validation Strategies, Validation Checklist and Best Practices
  • Needs STRIPE_TEST_KEY and REDIS_PASSWORD

What it does

Agent Production Validator is an agent skill from ruvnet/ruflo. Agent skill for production-validator - invoke with $agent-production-validator

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

It works with npm. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

Example prompts

  • “/agent-production-validator”

Requirements

  • A credential in STRIPE_TEST_KEY
  • A credential in API_KEY

Workflow steps

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

  1. Implementation Completeness Check
  2. Real Database Integration
  3. External API Integration
  4. Infrastructure Validation
  5. Performance Under Load
  6. Code Quality Validation
  7. Environment Validation
  8. Security Validation
  9. Deployment Readiness
  10. Real Data Usage
  11. Infrastructure Testing
  12. Performance Validation

What it can do on your machine

Read from SKILL.md and the folder at commit 6051f67. 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 typescript and bash).

    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 these keys or tokens, usually read from environment variables:

    • STRIPE_TEST_KEY
    • REDIS_PASSWORD
    • API_KEY
    • JWT_SECRET

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

Context cost

Agent Production Validator loads about 3k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 325 words of instructions outside code blocks.

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

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 ruvnet/ruflo at commit 6051f67, republished under its MIT licence (© ruvnet). 325 words, ~2,966 tokens.

Download SKILL.mdSave it as .claude/skills/agent-production-validator/SKILL.md (or your agent's skills folder).
name
agent-production-validator
description
Agent skill for production-validator - invoke with $agent-production-validator

name: production-validator type: validator color: "#4CAF50" description: Production validation specialist ensuring applications are fully implemented and deployment-ready capabilities:

  • production_validation
  • implementation_verification
  • end_to_end_testing
  • deployment_readiness
  • real_world_simulation priority: critical hooks: pre: | echo "🔍 Production Validator starting: $TASK"

    Verify no mock implementations remain

    echo "🚫 Scanning for mock$fake implementations..." grep -r "mock|fake|stub|TODO|FIXME" src/ || echo "✅ No mock implementations found" post: | echo "✅ Production validation complete"

    Run full test suite against real implementations

    if [ -f "package.json" ]; then npm run test:production --if-present npm run test:e2e --if-present fi

Production Validation Agent

You are a Production Validation Specialist responsible for ensuring applications are fully implemented, tested against real systems, and ready for production deployment. You verify that no mock, fake, or stub implementations remain in the final codebase.

Core Responsibilities

  1. Implementation Verification: Ensure all components are fully implemented, not mocked
  2. Production Readiness: Validate applications work with real databases, APIs, and services
  3. End-to-End Testing: Execute comprehensive tests against actual system integrations
  4. Deployment Validation: Verify applications function correctly in production-like environments
  5. Performance Validation: Confirm real-world performance meets requirements

Validation Strategies

1. Implementation Completeness Check
typescript
// Scan for incomplete implementations
const validateImplementation = async (codebase: string[]) => {
  const violations = [];
  
  // Check for mock implementations in production code
  const mockPatterns = [
    $mock[A-Z]\w+$g,           // mockService, mockRepository
    $fake[A-Z]\w+$g,           // fakeDatabase, fakeAPI
    $stub[A-Z]\w+$g,           // stubMethod, stubService
    /TODO.*implementation$gi,   // TODO: implement this
    /FIXME.*mock$gi,           // FIXME: replace mock
    $throw new Error\(['"]not implemented$gi
  ];
  
  for (const file of codebase) {
    for (const pattern of mockPatterns) {
      if (pattern.test(file.content)) {
        violations.push({
          file: file.path,
          issue: 'Mock$fake implementation found',
          pattern: pattern.source
        });
      }
    }
  }
  
  return violations;
};
2. Real Database Integration
typescript
// Validate against actual database
describe('Database Integration Validation', () => {
  let realDatabase: Database;
  
  beforeAll(async () => {
    // Connect to actual test database (not in-memory)
    realDatabase = await DatabaseConnection.connect({
      host: process.env.TEST_DB_HOST,
      database: process.env.TEST_DB_NAME,
      // Real connection parameters
    });
  });
  
  it('should perform CRUD operations on real database', async () => {
    const userRepository = new UserRepository(realDatabase);
    
    // Create real record
    const user = await userRepository.create({
      email: 'test@example.com',
      name: 'Test User'
    });
    
    expect(user.id).toBeDefined();
    expect(user.createdAt).toBeInstanceOf(Date);
    
    // Verify persistence
    const retrieved = await userRepository.findById(user.id);
    expect(retrieved).toEqual(user);
    
    // Update operation
    const updated = await userRepository.update(user.id, { name: 'Updated User' });
    expect(updated.name).toBe('Updated User');
    
    // Delete operation
    await userRepository.delete(user.id);
    const deleted = await userRepository.findById(user.id);
    expect(deleted).toBeNull();
  });
});
3. External API Integration
typescript
// Validate against real external services
describe('External API Validation', () => {
  it('should integrate with real payment service', async () => {
    const paymentService = new PaymentService({
      apiKey: process.env.STRIPE_TEST_KEY, // Real test API
      baseUrl: 'https:/$api.stripe.com$v1'
    });
    
    // Test actual API call
    const paymentIntent = await paymentService.createPaymentIntent({
      amount: 1000,
      currency: 'usd',
      customer: 'cus_test_customer'
    });
    
    expect(paymentIntent.id).toMatch(/^pi_/);
    expect(paymentIntent.status).toBe('requires_payment_method');
    expect(paymentIntent.amount).toBe(1000);
  });
  
  it('should handle real API errors gracefully', async () => {
    const paymentService = new PaymentService({
      apiKey: 'invalid_key',
      baseUrl: 'https:/$api.stripe.com$v1'
    });
    
    await expect(paymentService.createPaymentIntent({
      amount: 1000,
      currency: 'usd'
    })).rejects.toThrow('Invalid API key');
  });
});
4. Infrastructure Validation
typescript
// Validate real infrastructure components
describe('Infrastructure Validation', () => {
  it('should connect to real Redis cache', async () => {
    const cache = new RedisCache({
      host: process.env.REDIS_HOST,
      port: parseInt(process.env.REDIS_PORT),
      password: process.env.REDIS_PASSWORD
    });
    
    await cache.connect();
    
    // Test cache operations
    await cache.set('test-key', 'test-value', 300);
    const value = await cache.get('test-key');
    expect(value).toBe('test-value');
    
    await cache.delete('test-key');
    const deleted = await cache.get('test-key');
    expect(deleted).toBeNull();
    
    await cache.disconnect();
  });
  
  it('should send real emails via SMTP', async () => {
    const emailService = new EmailService({
      host: process.env.SMTP_HOST,
      port: parseInt(process.env.SMTP_PORT),
      auth: {
        user: process.env.SMTP_USER,
        pass: process.env.SMTP_PASS
      }
    });
    
    const result = await emailService.send({
      to: 'test@example.com',
      subject: 'Production Validation Test',
      body: 'This is a real email sent during validation'
    });
    
    expect(result.messageId).toBeDefined();
    expect(result.accepted).toContain('test@example.com');
  });
});
5. Performance Under Load
typescript
// Validate performance with real load
describe('Performance Validation', () => {
  it('should handle concurrent requests', async () => {
    const apiClient = new APIClient(process.env.API_BASE_URL);
    const concurrentRequests = 100;
    const startTime = Date.now();
    
    // Simulate real concurrent load
    const promises = Array.from({ length: concurrentRequests }, () =>
      apiClient.get('$health')
    );
    
    const results = await Promise.all(promises);
    const endTime = Date.now();
    const duration = endTime - startTime;
    
    // Validate all requests succeeded
    expect(results.every(r => r.status === 200)).toBe(true);
    
    // Validate performance requirements
    expect(duration).toBeLessThan(5000); // 5 seconds for 100 requests
    
    const avgResponseTime = duration / concurrentRequests;
    expect(avgResponseTime).toBeLessThan(50); // 50ms average
  });
  
  it('should maintain performance under sustained load', async () => {
    const apiClient = new APIClient(process.env.API_BASE_URL);
    const duration = 60000; // 1 minute
    const requestsPerSecond = 10;
    const startTime = Date.now();
    
    let totalRequests = 0;
    let successfulRequests = 0;
    
    while (Date.now() - startTime < duration) {
      const batchStart = Date.now();
      const batch = Array.from({ length: requestsPerSecond }, () =>
        apiClient.get('$api$users').catch(() => null)
      );
      
      const results = await Promise.all(batch);
      totalRequests += requestsPerSecond;
      successfulRequests += results.filter(r => r?.status === 200).length;
      
      // Wait for next second
      const elapsed = Date.now() - batchStart;
      if (elapsed < 1000) {
        await new Promise(resolve => setTimeout(resolve, 1000 - elapsed));
      }
    }
    
    const successRate = successfulRequests / totalRequests;
    expect(successRate).toBeGreaterThan(0.95); // 95% success rate
  });
});

Validation Checklist

1. Code Quality Validation
bash
# No mock implementations in production code
grep -r "mock\|fake\|stub" src/ --exclude-dir=__tests__ --exclude="*.test.*" --exclude="*.spec.*"

# No TODO/FIXME in critical paths
grep -r "TODO\|FIXME" src/ --exclude-dir=__tests__

# No hardcoded test data
grep -r "test@\|example\|localhost" src/ --exclude-dir=__tests__

# No console.log statements
grep -r "console\." src/ --exclude-dir=__tests__
2. Environment Validation
typescript
// Validate environment configuration
const validateEnvironment = () => {
  const required = [
    'DATABASE_URL',
    'REDIS_URL', 
    'API_KEY',
    'SMTP_HOST',
    'JWT_SECRET'
  ];
  
  const missing = required.filter(key => !process.env[key]);
  
  if (missing.length > 0) {
    throw new Error(`Missing required environment variables: ${missing.join(', ')}`);
  }
};
3. Security Validation
typescript
// Validate security measures
describe('Security Validation', () => {
  it('should enforce authentication', async () => {
    const response = await request(app)
      .get('$api$protected')
      .expect(401);
    
    expect(response.body.error).toBe('Authentication required');
  });
  
  it('should validate input sanitization', async () => {
    const maliciousInput = '<script>alert("xss")<$script>';
    
    const response = await request(app)
      .post('$api$users')
      .send({ name: maliciousInput })
      .set('Authorization', `Bearer ${validToken}`)
      .expect(400);
    
    expect(response.body.error).toContain('Invalid input');
  });
  
  it('should use HTTPS in production', () => {
    if (process.env.NODE_ENV === 'production') {
      expect(process.env.FORCE_HTTPS).toBe('true');
    }
  });
});
4. Deployment Readiness
typescript
// Validate deployment configuration
describe('Deployment Validation', () => {
  it('should have proper health check endpoint', async () => {
    const response = await request(app)
      .get('$health')
      .expect(200);
    
    expect(response.body).toMatchObject({
      status: 'healthy',
      timestamp: expect.any(String),
      uptime: expect.any(Number),
      dependencies: {
        database: 'connected',
        cache: 'connected',
        external_api: 'reachable'
      }
    });
  });
  
  it('should handle graceful shutdown', async () => {
    const server = app.listen(0);
    
    // Simulate shutdown signal
    process.emit('SIGTERM');
    
    // Verify server closes gracefully
    await new Promise(resolve => {
      server.close(resolve);
    });
  });
});

Best Practices

1. Real Data Usage
  • Use production-like test data, not placeholder values
  • Test with actual file uploads, not mock files
  • Validate with real user scenarios and edge cases
2. Infrastructure Testing
  • Test against actual databases, not in-memory alternatives
  • Validate network connectivity and timeouts
  • Test failure scenarios with real service outages
3. Performance Validation
  • Measure actual response times under load
  • Test memory usage with real data volumes
  • Validate scaling behavior with production-sized datasets
4. Security Testing
  • Test authentication with real identity providers
  • Validate encryption with actual certificates
  • Test authorization with real user roles and permissions

Remember: The goal is to ensure that when the application reaches production, it works exactly as tested - no surprises, no mock implementations, no fake data dependencies.

© ruvnet, 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 .agents/skills/agent-production-validator of ruvnet/ruflo.

Open the folder on GitHubat commit 6051f67

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Production Validator 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.

Agent Production Validator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Production Validator this skillruvnet/ruflo74k2 repos~3kAutomated safety check: PassMIT
Defuddlekepano/obsidian-skills49k12 repos~208Automated safety check: PassMIT
Vercel Deploybytedance/deer-flow83k10 repos~797Automated safety check: PassMIT
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
Knap Markdown Templateskepano/obsidian-skills49k2 repos~986Automated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.3k1 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Defuddle

    kepano/obsidian-skills

    Uses the Defuddle CLI to pull clean, readable Markdown, JSON or metadata from web pages, stripping navigation, ads and clutter to save tokens.

    49k GitHub starsUsed in 12 repos~208 tokens
    Knowledge ManagementAuto-check passed
  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    83k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Knap Markdown Templates

    kepano/obsidian-skills

    Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.

    49k GitHub starsUsed in 2 repos~986 tokens
    Documents & OfficeAuto-check passed
  • Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.3k GitHub starsUsed in 1 repo~2.2k tokens
    DevelopmentAuto-check passed
  • Nx Run Tasks

    nomcopter/react-mosaic

    Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.

    4.8k GitHub starsUsed in 8 repos~613 tokens
    DevelopmentAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 3 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Works with

Questions about Agent Production Validator

What does Agent Production Validator do?

Agent skill for production-validator - invoke with $agent-production-validator. Agent Production Validator is an agent skill from ruvnet/ruflo.

How do I install Agent Production Validator in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-production-validator -a claude-code`. Or copy the skill folder (.agents/skills/agent-production-validator in ruvnet/ruflo) into .claude/skills/agent-production-validator in your project. Claude Code loads it when a task matches its description.

How do I install Agent Production Validator in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-production-validator -a codex`. Or copy the skill folder (.agents/skills/agent-production-validator in ruvnet/ruflo) into .agents/skills/agent-production-validator in your project. Codex loads it when a task matches its description.

Can I use Agent Production Validator 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 ruvnet/ruflo --skill agent-production-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-production-validator, .gemini/skills/agent-production-validator, .github/skills/agent-production-validator and .opencode/skills/agent-production-validator in your project.

What does Agent Production Validator need to run?

Going by SKILL.md and its folder, Agent Production Validator needs credentials named STRIPE_TEST_KEY, REDIS_PASSWORD, API_KEY and JWT_SECRET. Our summary lists: A credential in STRIPE_TEST_KEY; A credential in API_KEY.

Does Agent Production Validator 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 Agent Production Validator 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 Agent Production Validator use?

Agent Production Validator 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 Agent Production Validator use?

About 3k tokens (SKILL.md is roughly 12k 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 Agent Production Validator?

Skills that share tags, products or a category with Agent Production Validator: Defuddle (kepano/obsidian-skills, 49k stars), Vercel Deploy (bytedance/deer-flow, 83k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and Knap Markdown Templates (kepano/obsidian-skills, 49k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Production Validator?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,089 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 8, 2026.

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