Agent skill

Engineering Wisdom

by hoangnb24 in hoangnb24/repository-harness

Use only when the user explicitly invokes $engineering-wisdom.

MITAuto-check passedAgent Workflows

Install Engineering Wisdom

skills CLI
$ npx skills add hoangnb24/repository-harness --skill engineering-wisdom -a claude-code

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

GitHub CLI
$ gh skill install hoangnb24/repository-harness engineering-wisdom --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/hoangnb24/repository-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/engineering-wisdom .claude/skills/engineering-wisdom && 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
engineering-wisdom
GitHub stars
1.2k
Token cost
~910 tokens
SKILL.md length
400 words
Files
4 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Use only when the user explicitly invokes $engineering-wisdom.

  • Works in 5 steps: Read AGENTS.md, docs/WORKFLOW.md, and… → Confirm that the user explicitly invoked… → Determine whether the request is… → …
  • Explicitly invokes $engineering-wisdom
  • SKILL.md covers Establish Scope, Review From Evidence, Advise Before Enforcing and Response Shape
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Engineering Wisdom is an agent skill from hoangnb24/repository-harness. Use only when the user explicitly invokes $engineering-wisdom. Provide repository-grounded engineering advice using contextual heuristics. Advice does not establish repository policy or authorize an architecture rewrite.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/heuristics.md` and `references/sources.md`).

It sits in Agent Workflows. The repository describes itself as: Turn any repo into an agent-ready workspace for Claude Code, Codex, Cursor, and other coding agents. The licence is MIT.

When your agent uses it

  • Explicitly invokes $engineering-wisdom

Example prompts

  • “/engineering-wisdom”

Workflow steps

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

  1. Read AGENTS.md, docs/WORKFLOW.md, and only the repository material
  2. Confirm that the user explicitly invoked this skill. Installation alone is
  3. Determine whether the request is advice/review or an authorized change.
  4. Read references/heuristics.md. Select only
  5. When the request crosses a host boundary, inspect the composition root,

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Engineering Wisdom loads about 910 tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 400 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~910
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

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 hoangnb24/repository-harness at commit 485fd40, republished under its MIT licence (© hoangnb24). 400 words, ~910 tokens.

Download SKILL.mdSave it as .claude/skills/engineering-wisdom/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
engineering-wisdom
description
Use only when the user explicitly invokes `$engineering-wisdom`. Provide repository-grounded engineering advice using contextual heuristics. Advice does not establish repository policy or authorize an architecture rewrite.

Engineering Wisdom

Give practical advice without treating a school of thought as universal law. Repository intent, code, tests, and observed behavior remain authoritative.

Establish Scope

  1. Read AGENTS.md, docs/WORKFLOW.md, and only the repository material relevant to the request.
  2. Confirm that the user explicitly invoked this skill. Installation alone is not activation.
  3. Determine whether the request is advice/review or an authorized change. Keep reviews read-only. For changes, follow repository authority and validation rules before editing.
  4. Read references/heuristics.md. Select only heuristics that match observed evidence. Read references/sources.md when attribution or the intellectual basis matters.
  5. When the request crosses a host boundary, inspect the composition root, external input, adapter semantics, shipped artifact, and cumulative state that are relevant. Do not assume isolated core tests prove those boundaries.

Review From Evidence

For each material finding, keep these fields separate:

  • Observation: A concrete repository fact with a path, symbol, test, command result, or behavior.
  • Heuristic: One named rule of thumb from the catalog and why it may apply.
  • Trade-off: Counter-pressure, cost, or a condition under which following the heuristic would make the system worse.
  • Proposed repository-owned enforcement: Either None, or a separately labeled proposal naming the repository owner, authority still required, possible mechanism, and removal condition. Never describe advice as an existing rule unless repository evidence already establishes it.
  • Verification: A focused observation or executable check that could confirm or falsify the recommendation. Match proof to the claim: test pure policy in isolation, startup at the composition root, and delivery through the artifact users actually load.

Rank findings by user impact and change risk. Prefer one concrete example over several abstract claims.

Show full SKILL.md (129 more words)Show less

Advise Before Enforcing

  • Do not rewrite application architecture merely because a heuristic suggests a different shape.
  • Do not introduce interfaces, layers, tests, linters, size limits, coverage targets, or dependency rules without repository-owned authority.
  • Propose the smallest reversible experiment when evidence is incomplete.
  • Preserve a deliberate duplication, coupling, integration test, or framework dependency when its local benefit outweighs the heuristic.
  • Say when no catalog heuristic materially improves the observed code.

If the user requests implementation and authority is sufficient, make the smallest coherent change and run the repository's own proof. Keep the review rationale separate from the evidence that the change works.

Response Shape

Start with the outcome in one sentence. Then report only material findings:

text
Finding: <specific effect>
Observation: <repository evidence>
Heuristic: <contextual rule of thumb and applicability>
Trade-off: <counter-pressure or harm condition>
Proposed repository-owned enforcement: None | <owner, missing authority,
mechanism, removal condition>
Verification: <command, test, measurement, or observation>

End with unresolved risks or None. Do not add a policy checklist by default.

© hoangnb24, 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 3 other files (references) in .agents/skills/engineering-wisdom of hoangnb24/repository-harness.

  • SKILL.md
  • agents/openai.yaml
  • references/heuristics.md
  • references/sources.md

Open the folder on GitHubat commit 485fd40

Compare with similar skills

Engineering Wisdom 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.

Engineering Wisdom compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Engineering Wisdom this skillhoangnb24/repository-harness1.2k—~910Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from hoangnb24/repository-harness

  • Audit Onboarding Proposal

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $audit-onboarding-proposal.

    1.2k GitHub stars~4k tokensUpdated 5 days ago
    Auto-check passed
  • Onboard Repository

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $onboard-repository.

    1.2k GitHub stars~6.8k tokensUpdated 5 days ago
    Auto-check: notes
  • Improve Harness

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $improve-harness. An agent skill from hoangnb24/repository-harness.

    1.2k GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed
  • Encode Invariant

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $encode-invariant.

    1.2k GitHub stars~668 tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Engineering Wisdom

What does Engineering Wisdom do?

Use only when the user explicitly invokes $engineering-wisdom. Engineering Wisdom is an agent skill from hoangnb24/repository-harness. Use only when the user explicitly invokes $engineering-wisdom.

When should I use Engineering Wisdom?

Engineering Wisdom fits situations like: explicitly invokes $engineering-wisdom.

How do I install Engineering Wisdom in Claude Code?

Run `npx skills add hoangnb24/repository-harness --skill engineering-wisdom -a claude-code`. Or copy the skill folder (.agents/skills/engineering-wisdom in hoangnb24/repository-harness) into .claude/skills/engineering-wisdom in your project. Claude Code loads it when a task matches its description.

How do I install Engineering Wisdom in Codex?

Run `npx skills add hoangnb24/repository-harness --skill engineering-wisdom -a codex`. Or copy the skill folder (.agents/skills/engineering-wisdom in hoangnb24/repository-harness) into .agents/skills/engineering-wisdom in your project. Codex loads it when a task matches its description.

Can I use Engineering Wisdom 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 hoangnb24/repository-harness --skill engineering-wisdom -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/engineering-wisdom, .gemini/skills/engineering-wisdom, .github/skills/engineering-wisdom and .opencode/skills/engineering-wisdom in your project.

What does Engineering Wisdom need to run?

SKILL.md names no scripts, command-line tools or credentials: Engineering Wisdom is instructions for the agent only.

Does Engineering Wisdom access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Engineering Wisdom 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 Engineering Wisdom use?

Engineering Wisdom 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 Engineering Wisdom use?

About 910 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.

What are the alternatives to Engineering Wisdom?

Skills that share tags, products or a category with Engineering Wisdom: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Engineering Wisdom?

hoangnb24 (a GitHub user) maintains it in hoangnb24/repository-harness, which has 1,242 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 4, 2026.

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