db-expert

Provide a no-op skill for validating discovery and orchestration in tests.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill db-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-expert
Source: https://github.com/danmestas/wardrobe/tree/main/hooks/monorepo-profiles/test/fixtures/sample/services/api/.claude/skills/db-expert
Command: npx skills add https://github.com/danmestas/wardrobe --skill db-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixture Skill used as a no-op to validate skill discovery and activation flows in tests without performing any real work.

Core Features & Use Cases

  • No-op fixture to exercise the skill-loading, activation, and orchestration pipelines during CI.
  • Lightweight placeholder for integration tests that require a valid Skill Unit structure without side effects.

Quick Start

Execute the db-expert skill in test harness scenarios to confirm fixture loading works as intended.

Frequently Asked Questions about db-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test skill discovery pipelines without triggering side effects?

A no-op fixture skill validates skill discovery and activation pipelines during integration tests without executing real processing logic or triggering system side effects.

What is a no-op fixture used for in monorepo integration testing?

A no-op fixture in monorepo integration testing provides a lightweight placeholder satisfying valid Skill Unit structure requirements, enabling orchestration pipelines to exercise loading and activation safely.

Can I use a fixture skill to validate CI orchestration flows in a monorepo?

Yes, a fixture skill validates CI orchestration flows in monorepo profiles by exposing required frontmatter with name and description and maintaining a minimal no-operation body, ensuring no real work executes.

Does a no-op skill require any dependencies to run fixture validation?

No, a no-op skill requires zero dependencies for fixture validation, relying solely on its minimal frontmatter and no-operation body to satisfy the Skill Unit spec within test harness scenarios.

When should I use a no-op fixture instead of a real skill for testing?

Use a no-op fixture instead of a real skill when confirming skill-loading and activation pipelines in CI without the overhead, side effects, or complexity of executing actual processing logic.