Skip to content
Back to skills

workflow-policy-layering

ASecurity

Separate workflow instructions from safety, authority, escalation, and validation rules. Use when an assistant, agent, or skill pack is getting muddled because process steps, permissions, forbidden actions, and review gates are mixed together.

  • 16 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added June 15, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned June 15, 2026

npx -y skills add markoblogo/abvx-agent-skills --skill workflow-policy-layering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of workflow-policy-layering?

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

Security grade badge for workflow-policy-layering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/markoblogo-workflow-policy-layering/badge)](https://www.skillsdirectory.com/skills/markoblogo-workflow-policy-layering)

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: workflow-policy-layering
description: Separate workflow instructions from safety, authority, escalation, and validation rules. Use when an assistant, agent, or skill pack is getting muddled because process steps, permissions, forbidden actions, and review gates are mixed together.
license: MIT
metadata:
  abvx_status: experimental
  abvx_origin: original
---

# Workflow Policy Layering

Separate operating workflow from policy and authority.

## Goal

Turn a messy assistant spec into clear layers:

- workflow;
- authority and boundaries;
- escalation;
- validation.

## Workflow

1. **Extract the workflow**
   - write the actual operating sequence without policy noise;
   - keep it in business or task language.
2. **Extract authority separately**
   - list what the assistant may do directly;
   - list what requires confirmation;
   - list what is forbidden.
3. **Extract escalation paths**
   - define what should be handed to a human, another role, or another system;
   - make the next step concrete instead of vague refusal.
4. **Extract validation**
   - define what should be checked before a response, mutation, recommendation, or delivery is considered complete;
   - keep this as a short checklist or gate list.
5. **Rewrite the spec**
   - keep workflow in the main skill body;
   - keep detailed policy and validation in `references/` or clearly named sections;
   - ensure the assistant does not confuse “can explain” with “can execute”.
6. **Run a conflict check**
   - look for steps that assume authority the policy layer does not grant;
   - look for policy text that silently changes the workflow;
   - fix contradictions before release.

## Output Shape

Return:

- workflow layer;
- authority layer;
- escalation layer;
- validation layer;
- open contradictions, if any.

## Design Rules

- Do not hide forbidden actions inside workflow prose.
- Do not let validation sprawl into generic QA philosophy.
- Keep escalation concrete and actionable.
- Treat drafts, summaries, and recommendations as different from real execution authority.

Files in this skill

  • SKILL.md2 KB
  • SKILL_CARD.md1.4 KB
  • agents/openai.yaml257 B

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…