New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Chous

by managedcode in managedcode/dotnet-skills

Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate.

MITAuto-check passedDevelopment

Install Chous

skills CLI
$ npx skills add managedcode/dotnet-skills --skill chous -a claude-code

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills chous --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/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Chous/skills/chous .claude/skills/chous && 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
chous
GitHub stars
486
Token cost
~1.2k tokens
SKILL.md length
543 words
Files
2
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate.

  • Works in 7 steps: Define the structure problem first → Start from chous init or a known preset,… → Keep the checked-in .chous file readable… → …
  • : growing frontend trees
  • SKILL.md covers Trigger On, Do Not Use For, Inputs and Workflow, plus 6 more sections
  • Calls npx, rg and npm

What it does

Chous is an agent skill from managedcode/dotnet-skills. Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. USE FOR: growing frontend trees; naming, folder, or file-placement policy; CI checks for frontend layout drift. DO NOT USE FOR: semantic code bugs, type errors, or framework API misuse; CSS, HTML, or JS rule enforcement inside files. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `manifest.json`). Compatibility notes: Requires a repository with a meaningful frontend file tree and Node-based tooling or npx; Chous complements code linters and does not replace ESLint…

It sits in Development, covering Linting and formatting and Codebase knowledge for agents. It works with .NET and npm. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : growing frontend trees
  • File-placement policy
  • CI checks for frontend layout drift
  • : semantic code bugs

Example prompts

  • “/chous”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires a repository with a meaningful frontend file tree and Node-based tooling or `npx`; Chous complements code linters and does not replace ESLint, Stylelint, or runtime site audits.

Workflow steps

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

  1. Define the structure problem first
  2. Start from chous init or a known preset, then tighten only the rules the repo can explain.
  3. Keep the checked-in .chous file readable enough that future contributors understand the policy.
  4. Add repeatable commands such as
  5. Exclude generated folders, build artifacts, and vendored assets so the signal stays architectural.
  6. Use Chous as a supplement to semantic linters, not as their replacement.
  7. Re-run after moves or refactors to confirm the structure policy still matches the intended design.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. 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

    Shell commands in SKILL.md call:

    • npx
    • rg
    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, 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.

  • Compatibility

    Requires a repository with a meaningful frontend file tree and Node-based tooling or `npx`; Chous complements code linters and does not replace ESLint, Stylelint, or runtime site audits.

    From compatibility in the SKILL.md frontmatter.

Context cost

Chous loads about 1.2k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 543 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 543 words, ~1,152 tokens.

Download SKILL.mdSave it as .claude/skills/chous/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
chous
description
Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. USE FOR: growing frontend trees; naming, folder, or file-placement policy; CI checks for frontend layout drift. DO NOT USE FOR: semantic code bugs, type errors, or framework API misuse; CSS, HTML, or JS rule enforcement inside files. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a repository with a meaningful frontend file tree and Node-based tooling or `npx`; Chous complements code linters and does not replace ESLint, Stylelint, or runtime site audits.

Chous for Frontend File-Structure Linting in .NET Repositories

Trigger On

  • the repo has a growing frontend tree and the user asks about naming conventions, folder structure, or file placement rules
  • the repo wants to enforce layout policy for ClientApp/, src/, apps/, or packages/
  • architectural drift in the frontend file tree is a larger problem than syntax errors

Do Not Use For

  • semantic code bugs, type errors, or framework API misuse
  • CSS, HTML, or JS rule enforcement inside files
  • very small repos where a structure linter would add more ceremony than value

Inputs

  • the nearest AGENTS.md
  • package.json
  • any existing .chous file
  • the frontend tree that needs policy enforcement

Workflow

  1. Define the structure problem first:
    • naming convention drift
    • component placement
    • forbidden folders or files
    • monorepo frontend boundaries
  2. Start from chous init or a known preset, then tighten only the rules the repo can explain.
  3. Keep the checked-in .chous file readable enough that future contributors understand the policy.
  4. Add repeatable commands such as:
    • npx chous
  5. Exclude generated folders, build artifacts, and vendored assets so the signal stays architectural.
  6. Use Chous as a supplement to semantic linters, not as their replacement.
  7. Re-run after moves or refactors to confirm the structure policy still matches the intended design.

Bootstrap When Missing

  1. Detect current state:
    • rg --files -g 'package.json' -g '.chous'
    • rg -n '"chous"' --glob 'package.json' .
  2. Start with the official no-install or global paths:
    • npx chous
    • npm install -g chous
  3. Initialize config when the repo truly wants structure policy:
    • npx chous init
  4. Add a repeatable command to AGENTS.md and package.json, then verify with:
    • npx chous
  5. Return status: configured if the repo now has a checked-in structure-lint baseline, or status: improved if an existing baseline was tightened.
  6. Return status: not_applicable when the repo is too small or too fluid to justify a structure-lint gate right now.
Show full SKILL.md (232 more words)Show less

Handle Failures

  • If Chous flags large parts of the tree after the first rollout, the rule set is probably too strict for the repo's current maturity; start from the preset and tighten incrementally.
  • Generated or vendored folders should be excluded instead of repeatedly ignored in reviews.
  • If contributors cannot explain what a rule protects, simplify the .chous policy before enforcing it in CI.

Deliver

  • a checked-in frontend structure policy
  • repeatable file-tree linting commands
  • explicit exclusions for generated and vendored folders

Validate

  • the .chous rules reflect real architecture intent
  • generated output is excluded
  • Chous is used alongside, not instead of, semantic linters
  • the policy remains understandable after the first rollout

Ralph Loop

  1. Plan: analyze current state, target outcome, constraints, and risks.
  2. Execute one step and produce a concrete delta.
  3. Review the result and capture findings.
  4. Apply fixes in small batches and rerun checks.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with a reason.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current step
  • actions_taken: concrete changes made
  • verification: commands, checks, or review evidence
  • remaining: unresolved items or none

Example Requests

  • "Enforce frontend folder naming and placement rules."
  • "Add file-structure linting to the web client."
  • "Why is our frontend tree drifting even though code linting passes?"

© managedcode, MIT. 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 1 other file in catalog/Tools/Chous/skills/chous of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Chous 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.

Chous compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chous this skillmanagedcode/dotnet-skills486—~1.2kAutomated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.2k—~2.2kAutomated safety check: PassMIT
Update .NET Supported OS Matrixdotnet/core22k—~4.1kAutomated safety check: PassMIT
Setup Pre Commitfossasia/eventyay-interpretation1.6k12 repos~565Automated safety check: PassApache-2.0
Releasehyhmrright/brooks-lint1.5k—~1.2kAutomated safety check: PassMIT
Msbuild Antipatternsrunceel/ReactiveProperty944—~3.7kAutomated safety check: PassMIT

Similar skills

  • Install Anti-Slop Oxlint Rules

    dmmulroy/anti-slop

    Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.2k GitHub stars~2.2k tokensUpdated 27 days ago
    DevelopmentAuto-check passed

  • Update .NET Supported OS Matrix

    dotnet/core

    Official

    Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.

    22k GitHub stars~4.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Setup Pre Commit

    fossasia/eventyay-interpretation

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo.

    1.6k GitHub starsUsed in 12 repos~565 tokens
    DevelopmentAuto-check passed

  • Release

    hyhmrright/brooks-lint

    Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…

    1.5k GitHub stars~1.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Msbuild Antipatterns

    runceel/ReactiveProperty

    Catalog of MSBuild anti-patterns with detection rules and fix recipes.

    944 GitHub stars~3.7k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Create Saleor Package

    saleor/apps

    Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Chous

What does Chous do?

Use Chous in .NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate. Chous is an agent skill from managedcode/dotnet-skills.NET repositories that ship sizeable frontend codebases and want file-structure linting, naming convention enforcement, and folder-layout policy as a CLI gate.

When should I use Chous?

Chous fits situations like: : growing frontend trees; file-placement policy; CI checks for frontend layout drift; : semantic code bugs.

How do I install Chous in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill chous -a claude-code`. Or copy the skill folder (catalog/Tools/Chous/skills/chous in managedcode/dotnet-skills) into .claude/skills/chous in your project. Claude Code loads it when a task matches its description.

How do I install Chous in Codex?

Run `npx skills add managedcode/dotnet-skills --skill chous -a codex`. Or copy the skill folder (catalog/Tools/Chous/skills/chous in managedcode/dotnet-skills) into .agents/skills/chous in your project. Codex loads it when a task matches its description.

Can I use Chous 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 managedcode/dotnet-skills --skill chous -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chous, .gemini/skills/chous, .github/skills/chous and .opencode/skills/chous in your project.

What does Chous need to run?

Going by SKILL.md and its folder, Chous needs the command-line tools its instructions call (npx, rg and npm). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires a repository with a meaningful frontend file tree and Node-based tooling or `npx`; Chous complements code linters and does not replace ESLint, Stylelint, or runtime site audits..

Does Chous access the network?

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

Is Chous 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. Review the folder before installing.

What licence does Chous use?

Chous is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Chous use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Chous?

Skills that share tags, products or a category with Chous: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars), Update .NET Supported OS Matrix (dotnet/core, 22k stars), Setup Pre Commit (fossasia/eventyay-interpretation, 1.6k stars) and Release (hyhmrright/brooks-lint, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chous?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

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