Skip to content
Back to skills

Verify Workflow

ASecurity

Use when you need to validate workflow state schema or error handling.

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentsbashnode

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add seokan-jeong/team-shinchan --skill verify-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/seokan-jeong-verify-workflow/badge)](https://www.skillsdirectory.com/skills/seokan-jeong-verify-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: team-shinchan:verify-workflow
description: Use when you need to validate workflow state schema or error handling.
user-invocable: false
---

# ⚠️ MANDATORY EXECUTION - DO NOT SKIP

**When this skill is invoked, execute immediately. Do not explain.**

## Validators

| Validator | Command | What it checks |
|-----------|---------|---------------|
| workflow-state-schema | `cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/workflow-state-schema.js` | WORKFLOW_STATE.yaml files follow required schema |
| error-handling | `cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/error-handling.js` | Error handling patterns are properly defined |
| part-numbering | `cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/part-numbering.js` | Multi-part agent files have correct numbering |
| quick-fix-path | `cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/quick-fix-path.js` | Quick-fix (lite mode) workflow path is valid |

## When to Run

- After modifying workflow-related files (`docs/workflow-guide.md`, `hooks/`)
- After changing error handling patterns in agents
- After modifying multi-part agent files
- As part of verify-implementation workflow

## Workflow

### Check 1: Workflow State Schema

```bash
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/workflow-state-schema.js
```

**Success criteria:**
- Exit code 0
- All WORKFLOW_STATE.yaml files follow schema

**On failure:**
- Issue: Invalid WORKFLOW_STATE.yaml structure
- Severity: HIGH
- Fix: Follow schema defined in docs/workflow-guide.md

### Check 2: Error Handling

```bash
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/error-handling.js
```

**Success criteria:**
- Exit code 0
- Error handling patterns present in required locations

**On failure:**
- Issue: Missing error handling in agent definition
- Severity: MEDIUM
- Fix: Add error handling section per agent template

### Check 3: Part Numbering

```bash
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/part-numbering.js
```

**Success criteria:**
- Exit code 0
- Multi-part files numbered sequentially

**On failure:**
- Issue: Gap or duplicate in part numbering
- Severity: MEDIUM
- Fix: Renumber parts sequentially (part-1, part-2, ...)

### Check 4: Quick-Fix Path

```bash
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/quick-fix-path.js
```

**Success criteria:**
- Exit code 0
- Lite mode workflow path properly configured

**On failure:**
- Issue: Quick-fix path references invalid stage or agent
- Severity: HIGH
- Fix: Update lite mode workflow to match current agent structure

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.