Agent skill

Audit Type Ownership

by compartmentdev in compartmentdev/compartment

Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

Apache-2.0Auto-check passedBackend & APIs

Install Audit Type Ownership

skills CLI
$ npx skills add compartmentdev/compartment --skill audit-type-ownership -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install compartmentdev/compartment audit-type-ownership --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/compartmentdev/compartment.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/audit-type-ownership .claude/skills/audit-type-ownership && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audit-type-ownership
GitHub stars
205
Token cost
~745 tokens
SKILL.md length
335 words
Files
3 (incl. scripts)
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

  • Works in 6 steps: Run node… → Narrow with --package when the request… → Read the script output before making… → …
  • Backend & APIs work in your project
  • SKILL.md covers Source of truth, Workflow, Default scope and Output, plus 1 more section
  • Runs JavaScript scripts from its folder; calls node and docker

What it does

Audit Type Ownership is an agent skill from compartmentdev/compartment. Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml`).

It sits in Backend & APIs. It works with Docker. The repository describes itself as: Compartment is a self-hosted deployment system for small software on infrastructure your team controls. The licence is Apache-2.0.

When your agent uses it

  • Backend & APIs work in your project

Example prompts

  • “/audit-type-ownership”

Requirements

  • Node.js
  • Docker

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Run node .codex/skills/audit-type-ownership/scripts/audit_type_ownership.mjs from the repo root.
  2. Narrow with --package when the request is scoped. Use --format json only when a structured artifact is more useful than Markdown.
  3. Read the script output before making claims. It is a heuristic inventory, not proof.
  4. Treat declared workspace dependencies as package context, not automatic findings. A non-contracts import matters only when it is…
  5. Treat duplicate names as move candidates only when they imply a shared serialized or cross-package owner. Package-local families such as…
  6. Classify findings with this matrix

What it can do on your machine

Read from SKILL.md and the folder at commit 15373e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audit Type Ownership loads about 745 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 335 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~745

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from compartmentdev/compartment at commit 15373e7, republished under its Apache-2.0 licence (© compartmentdev). 335 words, ~745 tokens.

Download SKILL.mdSave it as .claude/skills/audit-type-ownership/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
audit-type-ownership
description
Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

Audit Type Ownership

Use this skill for non-mutating type ownership audits in the compartment repo.

Source of truth

  • AGENTS.md
  • docs/layers/README.md
  • docs/specs/type-placement.md
  • the relevant layer docs, starting with docs/layers/api.md when the user does not narrow the audit

Workflow

  1. Run node .codex/skills/audit-type-ownership/scripts/audit_type_ownership.mjs from the repo root.
  2. Narrow with --package <api|contracts|sdk|cli|edge|worker|docker|kube-runtime|utils|test-support> when the request is scoped. Use --format json only when a structured artifact is more useful than Markdown.
  3. Read the script output before making claims. It is a heuristic inventory, not proof.
  4. Treat declared workspace dependencies as package context, not automatic findings. A non-contracts import matters only when it is undeclared in the owning package or it conflicts with the relevant layer doc.
  5. Treat duplicate names as move candidates only when they imply a shared serialized or cross-package owner. Package-local families such as *Input, *Context, *Plan, *Result, *Options, *State, *Config, and *App can legitimately exist in multiple packages.
  6. Classify findings with this matrix:
  • contracts: serialized DTOs, public *Request, *Response, *Summary, shared status/value aliases
  • query layer: *Row, *Selection, *Transaction, *Executor, persistence mutation inputs
  • service layer: *Input, *Context, *Plan, *Result
  • app/adapter layer: *Options, *State, *Config, *App
  1. Treat cross-process or cross-package payloads as contract-owned, even when the current consumer is internal.
  2. Treat query/service boundary leakage and placement violations from docs/specs/type-placement.md as ownership bugs, including generic src/types/, routes/shared/, and route DTO mappers outside *.presenter.ts.
  3. If the audit turns into implementation, run the narrowest relevant package checks first and then add any required special checks for the diff.

Default scope

  • Start with api.
  • Then sweep contracts, sdk, cli, edge, worker, docker, kube-runtime, utils, and test-support.
  • Keep the audit non-mutating unless the user explicitly asks for implementation after the audit.

Output

  • Policy
  • Concrete findings
  • Move list
  • Phased refactor plan

Script

  • scripts/audit_type_ownership.mjs inventories named interface and type declarations by package and file.
  • It highlights duplicate type names, suspicious @compartment/* imports, query/service leaks, root export risks, package dependency context, and placement violations.
  • Final ownership decisions still come from AGENTS.md, the architecture docs, and the relevant checks.

© compartmentdev, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .codex/skills/audit-type-ownership of compartmentdev/compartment.

  • SKILL.md
  • agents/openai.yaml
  • scripts/audit_type_ownership.mjs

Open the folder on GitHubat commit 15373e7

Compare with similar skills

Audit Type Ownership next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audit Type Ownership compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Type Ownership this skillcompartmentdev/compartment205—~745Automated safety check: PassApache-2.0
DormiceBitMiracle-AI/Dormice1.4k—~2.7kAutomated safety check: NotesApache-2.0
Running And Testing LocallyNangoHQ/nango13k—~3.8kAutomated safety check: NotesCustom licence
Compileapache/skywalking-nodejs180—~1.3kAutomated safety check: PassApache-2.0
Code Engine SpecialistIBM/CodeEngine117—~3.4kAutomated safety check: PassApache-2.0
Kratos Developmentaide-family/moon253—~1.5kAutomated safety check: PassNone

Similar skills

  • Dormice

    BitMiracle-AI/Dormice

    Operate Dormice self-hosted agent sandboxes — acquire a sandbox, run commands, move files, tune lifecycle policy — through the official E2B SDKs, the native HTTP API and SDK, or the dor CLI.

    1.4k GitHub stars~2.7k tokensUpdated 7 days ago
    Backend & APIsAuto-check: notes
  • A skill your agent uses when running the Nango application locally for development and browser testing - covers Docker services, dev commands, service URLs, and troubleshooting startup issues

    13k GitHub stars~3.8k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Compile

    apache/skywalking-nodejs

    Compile / build / type-check the skywalking-nodejs agent. An agent skill from apache/skywalking-nodejs.

    180 GitHub stars~1.3k tokensUpdated 22 days ago
    Backend & APIsAuto-check passed
  • Official

    Deploys, configures, and troubleshoots IBM Cloud Code Engine workloads using the ibmcloud ce CLI.

    117 GitHub stars~3.4k tokensUpdated today
    Backend & APIsAuto-check passed
  • Kratos Development

    aide-family/moon

    Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.

    253 GitHub stars~1.5k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed
  • Francis Thinking

    francis-build/francis

    Invoke on ANY Francis task — routes, WebSocket, SSE, streaming, real-time, chat, Plug middleware, auth, CORS, static assets, deploy, Dockerfile, JSON API, uploads, sessions, use Francis, ws/2…

    107 GitHub stars~3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

More from compartmentdev/compartment

All 12 skills in this repo
  • Open PR And Monitor

    compartmentdev/compartment

    Open or reuse a repo PR and monitor it with a five-minute Codex heartbeat until it is ready, terminal, or blocked.

    205 GitHub stars~470 tokensUpdated 1 mo ago
    Auto-check passed
  • Review A Change

    compartmentdev/compartment

    A skill your agent uses when the user invokes $review-a-change or asks for a compartment repo code review; always use the delegated subagent review path by splitting review into separate parallel…

    205 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Review Reuse And Dedup

    compartmentdev/compartment

    A skill your agent uses when reviewing compartment repo changes for existing helper reuse, extractable pure utilities, duplicated logic, repeated constants, hardcoded values, or repeated variable…

    205 GitHub stars~753 tokensUpdated 1 mo ago
    Auto-check passed
  • Compartment Smoke Test

    compartmentdev/compartment

    Run or delegate a browser-first smoke test of the local compartment through browser-use as a real user: boot or reuse the local stack, install or log in, deploy the repo smoke fixtures, verify CLI…

    205 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check: notes
  • Develop A Feature

    compartmentdev/compartment

    Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

    205 GitHub stars~554 tokensUpdated 1 mo ago
    Auto-check passed
  • Public Docs Maintenance

    compartmentdev/compartment

    Maintain the public Starlight docs site for material changes to shipped Compartment workflows, using generated reference where possible and concise task- and decision-focused guides elsewhere.

    205 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Audit Type Ownership

What does Audit Type Ownership do?

Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans. Audit Type Ownership is an agent skill from compartmentdev/compartment. Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

When should I use Audit Type Ownership?

Audit Type Ownership fits situations like: backend & APIs work in your project.

How do I install Audit Type Ownership in Claude Code?

Run `npx skills add compartmentdev/compartment --skill audit-type-ownership -a claude-code`. Or copy the skill folder (.codex/skills/audit-type-ownership in compartmentdev/compartment) into .claude/skills/audit-type-ownership in your project. Claude Code loads it when a task matches its description.

How do I install Audit Type Ownership in Codex?

Run `npx skills add compartmentdev/compartment --skill audit-type-ownership -a codex`. Or copy the skill folder (.codex/skills/audit-type-ownership in compartmentdev/compartment) into .agents/skills/audit-type-ownership in your project. Codex loads it when a task matches its description.

Can I use Audit Type Ownership in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add compartmentdev/compartment --skill audit-type-ownership -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-type-ownership, .gemini/skills/audit-type-ownership, .github/skills/audit-type-ownership and .opencode/skills/audit-type-ownership in your project.

What does Audit Type Ownership need to run?

Going by SKILL.md and its folder, Audit Type Ownership needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and docker). Our summary lists: Node.js; Docker.

Does Audit Type Ownership access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Audit Type Ownership safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Audit Type Ownership use?

Audit Type Ownership is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Type Ownership use?

About 745 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Audit Type Ownership?

Skills that share tags, products or a category with Audit Type Ownership: Dormice (BitMiracle-AI/Dormice, 1.4k stars), Running And Testing Locally (NangoHQ/nango, 13k stars), Compile (apache/skywalking-nodejs, 180 stars) and Code Engine Specialist (IBM/CodeEngine, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Type Ownership?

compartmentdev (a GitHub organization) maintains it in compartmentdev/compartment, which has 205 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 20, 2026.

Source: compartmentdev/compartment on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.