Individual skill

agentic-engineering

Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.

skills/agentic-engineering/SKILL.md

Read pinned source

Source commit 5a645148a108d71c76521715117b737ae60b1423

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 140
Repository last updated: Sep 19, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-skills Repository topic
agentic Repository topic
ai-agents Repository topic
cursor-rules Repository topic
knowledge-management Repository topic
obsidian Repository topic
codex Repository topic
ontology Repository topic
loop Repository topic
loop-engineering Repository topic
engineering Derived category
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,579 bytes

Read excerpt


# Agentic Engineering

<skill_contract>
  <input>An engineering objective, inspectable repository or workflow, acceptance criteria, permissions, risk, and state location.</input>
  <output>The smallest sufficient model-native process with bounded autonomy, evals, recovery, and verified write-back.</output>
  <done>Fresh task and adoption evidence support the observable end state without crossing authority boundaries.</done>
  <non_goals>Agent complexity for its own sake, premature multi-agent topology, or unverified knowledge promotion.</non_goals>

An agent is a stateful engineering process, not a prompt. Its quality ceiling is the combination of objective, context, tools, taste/evaluation, permissions, recovery, and feedback latency.

## Usage Template

Provide: engineering objective, repository/workflow, users, acceptance criteria, constraints, permissions, risk, current evidence, and durable state location.