Index of every page on this site: llms.txt
All skills
Run it yourself

Changes exactly what was asked, keeps what already worked and finishes every item in the message.

Use this Skill: https://skilld.dev/gh/raphaelsalaja/skills/scope

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈26 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈22 more on demand in 1 file.

Description uses 1.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈105 characters, or 1.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Scope

This skill holds an edit to the request. It reads the smallest literal meaning, keeps everything that already worked and accounts for every item the user sent.

The smallest reading wins

A change outside the named element is a finding unless the user asked for a sweep. One short question before a broad change is not a finding. Press hardest on short messages that point at one element, on batched messages and on refactors.

Deleting what nobody asked for belongs to restraint. Proving the change works belongs to verify. Writing a correction down as a rule belongs to rule.

Every ask gets an answer

Split the message into numbered items and add the open items from earlier turns. Close with the same list, each item done or not done with the reason. Doing the first of four asks is scope-list-every-ask.

A message sent while you work adds items to the list. It cancels nothing unless it says stop or replaces an item by name.

The named element and nothing around it

Restate the target in a few words. "The card" means the card, not the page around it. Restyling the whole shell for a top bar request is scope-smallest-reading.

Read "this", "it" and "here" as what the user last pointed at: the attached screenshot, the selected code or the last item named.

Ask only what the code cannot answer

Search the repository before asking. Where a file lives, which component renders a screen and what a value is now are lookups, not questions. Asking one is scope-search-before-asking.

Ask about intent: which of two readings fits, or a value only the user knows. Ask once, in one short question that names both readings and the one you would take.

Earlier instructions still stand

Before editing, read the user's earlier corrections in the thread and the rules in AGENTS.md, CLAUDE.md and the editor rule folders. The rule file nearest the edited path wins, and the user's message outranks every file. Re-adding something they removed, or a pill button where a rule forbids pills, is scope-remember-instructions. A value they gave, such as 16px of left padding, stays. Guessing a new one is scope-keep-given-values.

When two of the user's instructions conflict, the later one wins. Say which earlier one it replaced. Applying the older one is scope-later-wins.

The named approach or a stated reason

When the user names an approach, a file or a library, use it. When it cannot work, stop and say why before building something else. Shipping a different approach without a word is scope-say-the-substitution.

What worked keeps working

Before a refactor, list the features, buttons and states that exist now, then check each one after. A dropped back button is scope-keep-what-worked. When fixing one property, keep the others. Fixing a clip by removing the width animation is scope-no-collateral.

Unshipped work is done now

Work that has not shipped is not split into phases or marked out of scope without asking. A "phase 2" list is scope-no-phasing. While planning, plan only. Editing files before the plan is approved is scope-plan-means-plan.

An explanation is the answer

When the user asks how something works, explain it and wait. Answering "how does this work" with a diff is scope-explain-when-asked.

A question about the code, such as "why does the header jump?", gets an answer first. A request phrased as a question, such as "can you tighten the gap?", is a request.

The pair

Every check is a pair. The broken line sits beside the line that replaces it.

Rule Broken Replacement
scope-list-every-ask The first of four asks done, three dropped Four numbered items, each reported
scope-smallest-reading "Fix the top bar" restyles the whole shell Only the top bar changes
scope-search-before-asking "Which file renders the sidebar?" Sidebar.tsx found by search, then "Collapse it on phones too? I would leave phones as they are."
scope-remember-instructions Dots the user removed come back, or a pill button in a repo whose rules forbid pills Earlier turns and the rule files read before editing
scope-keep-given-values Left padding re-guessed as 12px The 16px the user gave
scope-later-wins The 12px from turn 2 applied after turn 5 said 16px 16px, with "replaces the 12px from earlier"
scope-say-the-substitution Asked for a CSS fix, a ResizeObserver shipped without a word "CSS cannot read the content height here. Use a ResizeObserver instead?"
scope-keep-what-worked A refactor drops back and forward buttons Before and after feature list, both buttons kept
scope-no-collateral The clip is fixed and the width animation is gone Clip fixed, width animation kept
scope-no-phasing "Saved filters: phase 2" Built now, or one question
scope-plan-means-plan Files edited during planning Plan only until it is approved
scope-explain-when-asked "Explain how it works" answered with a diff An explanation, then wait

Reporting

Severity. HIGH is a dropped feature or property, an earlier instruction or written rule undone or a value the user gave replaced. MEDIUM is a change outside the named element, or an ask left unreported. It is also an older instruction applied over a later one, or a named approach swapped without a word. So is a "phase 2" list, a file edited during planning or a diff given where an explanation was asked. LOW is a question asked where one reading was plain, or one the repository already answered.

Format. One finding per root cause, citing the request when no file applies:

file:line - [rule-id] what is wrong
request 2 - [rule-id] what is wrong

Then a Rule | Count | Severity summary. Block when any HIGH remains, Approve otherwise. Never Approve a diff you did not read. Mark every check you could not run as Not verified.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The analyzed skill provides instructional guidelines for the agent to maintain focus and precision during code editing tasks. It does not contain any executable code, network operations, or malicious patterns.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at b2e4283. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated yesterday

README badge

README badge for raphaelsalaja/skills/scope