agentleFS
alilfrancesalilfrances/midas/skills/scope/SKILL.md

scope

Skill0 starsChanged 4 months agoMITView on GitHub

Accept/decline calibration. Use when task may exceed capabilities — missing tools, creds, device, network, domain — or when tempted to fake progress.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frames, develop and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sanmidableSkill

    frames

    Also in 3 projects that use this

  • hong9LeeSkill

    develop

    빌드, 아키텍처, git 관련 작업 시 OMS MSA 공통 인프라 규칙을 적용한다. 기술 스택, 빌드 명령, 헥사고날 아키텍처 구조, git 워크플로우, AI Context 동기화 규칙을 다룬다. 코드 작성 컨벤션은 /convention, 테스트 컨벤션은 /test-guide 스킬을 참조.

    Also in 6 projects that use this

  • minhtran3124Skill

    visual

    Skill graph visualizer — scans all SKILL.md files in skills/, builds a directed relationship graph from explicit `relationships` frontmatter (falling back to content inference), and generates both a Mermaid markdown summary and an interactive HTML graph at .docs/skill-graph.html. Trigger: /visual

    Also in 3 projects that use this

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 7 projects that use this

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 5 projects that use this

  • Skeln-ioSkill

    copy

    Direct response copywriting using proven frameworks. Brand-aware — reads ICP, voice, and tone from your brand config. Covers product descriptions, SEO meta, email, social, press angles.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before accepting task, 10-second audit:

    line 8
  2. Distinctive:

    Never fake it: no invented output, no pretend-verify, no silent partial delivery labeled done.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scope

Before accepting task, 10-second audit:

  1. Tools — needed tool/MCP/plugin present? Check available tools list, not memory. Missing: name it, offer nearest capable route.
  2. Access — creds, network, device, filesystem perms? Can't reach = can't verify = say so upfront.
  3. Knowledge — API/library moving fast or post-cutoff? Fetch current docs before acting (context7/WebFetch). Never code against remembered API when verify possible.
  4. Scale — task needs hours/parallel work? State honest scope, propose slice or subagent split.

Decline pattern (use when capability genuinely missing):

  • One line what blocks: "Cannot X: no Y."
  • One line nearest alternative: "Can do Z instead" or "needs user: run cmd".
  • Never fake it: no invented output, no pretend-verify, no silent partial delivery labeled done.
  • Record it: midas-lesson "declined X: no Y" — next session in this repo starts knowing the limit.

Accept pattern: state assumptions + what will be verified how. Partial capability = accept with explicit boundary, not silent shrink.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.