agent-as-function-audit

Audit multi-agent workflows for agent-as-function architecture conformance.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/skurekjakub/docwriter-agent --skill agent-as-function-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-as-function-audit
Source: https://github.com/skurekjakub/docwriter-agent/tree/main/.github/skills/agent-as-function-audit
Command: npx skills add https://github.com/skurekjakub/docwriter-agent --skill agent-as-function-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps practitioners verify that a multi-agent system genuinely follows the agent-as-function (pure-router) pattern, catching deviations where orchestration or subagents perform unintended work, data flows bypass routing, or artifact contracts drift.

Core Features & Use Cases

  • Inventory and compare orchestrator prompts, subagent prompts, and routing tables for architectural consistency.
  • Flag contract drift, status.json routing gaps, and differences between standard and revision flows.
  • Produce actionable findings with exact file references for remediation.

Quick Start

Provide a structured audit of an orchestrator plus its subagents to confirm agent-as-function conformance.

Frequently Asked Questions about agent-as-function-audit

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

FAQPage Schema
How do I audit multi-agent workflow routing for architectural conformance?▼

Audit multi-agent workflow routing by validating orchestrator and subagent prompts against the pure-router pattern, checking routing tables and artifact handoffs to surface ownership or leakage issues with exact file references.

What is the agent-as-function pattern for multi-agent orchestrators?▼

The agent-as-function pattern treats agents as pure routers, ensuring orchestration and subagents perform no unintended work and data flows strictly through defined routing and artifact contracts.

How do I find contract drift in subagent prompts and revision flows?▼

Find contract drift by inventorying and comparing subagent prompts, routing tables, and status.json validation across both standard and revision paths to identify routing gaps and naming inconsistencies.

Can I check transitive skill dependencies and versioned artifact handoffs?▼

Yes, you can check transitive skill dependencies and validate versioned artifacts by auditing artifact naming conventions, handoff patterns, and status.json routing to ensure strict architectural compliance.

Why does my multi-agent workflow bypass routing and leak data between subagents?▼

Data leaks between subagents occur when orchestration bypasses pure-router routing or artifact contracts drift; auditing prompts, routing tables, and handoff patterns identifies exact file references for remediation.