Agent skill · Security

dk-agent-native-audit

Run comprehensive agent-native architecture review with scored principles. Audits a codebase against 8 agent-native architecture principles (Action Parity, Tools as Primitives, Context Injection, Shared Workspace, CRUD Completeness, UI Integration, Capability Discovery, Prompt-Native Features) by launching parallel sub-agents and producing a scored report. Use when the user wants to evaluate how agent-friendly their architecture is, or audit specific principles. Triggers on: 'agent native audit', 'architecture review', 'how agent-friendly is this', or /dk-agent-native-audit.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill dk-agent-native-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Allowed tools: BashReadGrepGlobTask
Path: skills/analysis/dk-agent-native-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /dk-agent-native-audit — Agent-Native Architecture Review Conducts a comprehensive review of the codebase against agent-native architecture principles, launching parallel sub-agents for each principle and producing a scored report. ## Context <audit_context> $ARGUMENTS </audit_context> ## Core Principles | # | Principle | One-liner | |---|-----------|-----------| | 1 | Action Parity | Whatever the user can do, the agent can do | | 2 | Tools as Primitives | Tools provide capability, not behavior | | 3 | Context Injection | System prompt includes dynamic context about app state | | 4 | Shared Workspace | Agent and user work in the same data space | | 5 | CRUD Completeness | Every entity has full Create, Read, Update, Delete | | 6 | UI Integration | Agent actions immediately reflected in UI | | 7 | Capability Discovery | Users can discover what the agent can do | | 8 | Prompt-Native Features | Features are prompts defining outcomes, not code | ## Workflow ### Step 1: Load reference material Read `references/agent-prompts.md` in this skill's directory to get the detailed prompt for each sub-agent. That file contains the exact instructions, search strategies, and output format for all

What's inside
Steps it walks through
  1. Context
  2. Core Principles
  3. Workflow
  4. Step 1: Load reference material
  5. Step 2: Check for single-principle audit
  6. Step 3: Launch parallel sub-agents
  7. Step 4: Compile summary report
  8. Success criteria
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the dk-agent-native-audit skill do?

Run comprehensive agent-native architecture review with scored principles. Audits a codebase against 8 agent-native architecture principles (Action Parity, Tools as Primitives, Context Injection, Shared Workspace, CRUD Completeness, UI Integration, Capability Discovery, Prompt-Native Features) by launching parallel sub-agents and producing a scored report. Use when the user wants to evaluate how agent-friendly their architecture is, or audit specific principles. Triggers on: 'agent native audit', 'architecture review', 'how agent-friendly is this', or /dk-agent-native-audit.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill dk-agent-native-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going