Skip to content
Skills Library
AI & agents · Automation

context-engineering

/context-engineering

Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.

Licence
Apache-2.0
Last repository change
28.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.

Original author description

Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.

How it works

  1. Contract
  2. Inputs
  3. Procedure
  4. Failure and recovery
  5. Output
Original SKILL.md headings · 36 lines, 491 words
SKILL.md preview
---
name: context-engineering
description: 'Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.'
disable-model-invocation: true
---

# Context engineering

## Contract

| Field | Bound contract |
|---|---|
| Trigger | Long session has accumulated stale or conflicting context, or the user asks to refresh or recheck context before continuing. |
| Authority | Reversible local: writes only an optional scratch state note; rollback is undo. No remote mutation. |
| Side effect | Optional scratch state note only; no project files touched. |
| Done | Acting context is provably current and minimal; stale items are dropped with the user informed. |

## Inputs

- The current acting context present in the session: stated facts, assumptions, inferred file state, and prior decisions.
- The source of truth for each item being rechecked: repository files, tool output, or user-stated ground truth.
- Optional: a user-named subset to recheck. If omitted, recheck the full acting context.

## Procedure

1. Enumerate every item in the acting context: stated facts, assumptions, inferred file state, and prior decisions. Done when: every acting-context item is enumerated.
2. For each item, recheck it against its source of truth by the narrowest action that settles it: read the file, re-run the tool, or ask the user. Classify the item as current, stale, or contradicted. Done when: every item is classified current, stale, or contradicted.
3. Drop stale and contradicted items from the acting context. Replace a dropped item with the corrected value only when the source of truth supplies one. Done when: stale and contradicted items are dropped and replaced where a corrected value exists.
4. Remove redundant or duplicate items so the acting context holds only items that are provably current and needed for the remaining work. Done when: no redundant or duplicate items remain.
5. Tell the user which items were dropped and why, and identify any item that could not be settled because its source of truth was unreachable. Done when: dropped items and reasons are reported and unsettled items are identified.
6. Optionally write a scratch state note recording the settled context and the dropped items. Do not touch any project file. Done when: the scratch note is written or skipped, and no project file is touched.

## Failure and recovery
- Unreachable source of truth: leave the dependent item flagged as unsettled, do not drop or replace it, and report it to the user. Never assert an item is current without a settled source.
- Contradiction between sources: report both sources and ask the user which to keep. Do not silently pick one.
- Partial result: deliver the subset that was settled and explicitly list the unsettled remainder. Never present a partial refresh as complete.
- Non-mutation boundary: if any step would require touching a project file or remote state, stop and report the boundary rather than widening authority.

## Output
Refreshed acting context (only provably current, minimal items) → user-facing list of dropped items with reasons → optional scratch state note. Unsettled items listed separately and remain flagged.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · OutlineDriven/outline-driven-development90Apache-2.0
mvschwarz/openrig100Apache-2.0
TerminalSkills/skills100Apache-2.0
FrancoStino/opencode-skills-collection100MIT
drvoss/everything-copilot-cli100MIT
komluk/scaffolding100MIT
kdlbs/kandev100AGPL-3.0
proxify-dev/agentic-kit100MIT
krzysztofsurdy/code-virtuoso100MIT

Database snapshot: 13.11.2026 · package version 1895f0f4dbb0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90create-plugin-scaffold
    Use when asked to create a local agent-plugin directory tree or marketplace package. Not for remote, credential, publish, deploy, or irreversible changes.
  • 90create-branch
    Use when the user asks to create a new branch or start work on one. Not for remote, credential, publish, deploy, or irreversible changes.
  • 100append-run-log
    Use when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.
  • 98strict-validation-setup
    Use when a user invokes a strict-mode validation or verifiable-goals loop setup. Not for remote, credential, publish, deploy, or irreversible changes.
  • 100append-run-log
    Use when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.