agentleFS
Sign inStart free
fabioc-alohafabioc-aloha/Alex_ACT_ONE/skills/platform-awareness/SKILL.md

platform-awareness

Skill0 starsChanged 9 days agoMITView on GitHub

Discover current host capabilities and verify Copilot CLI/VS Code platform claims against native help and official documentation. Use for deferred tools, harness differences, native features, MCP/browser availability, and reproduced compatibility exceptions; do not assume historical settings or tool names.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the current host's tool discovery, help, settings inspection, and official documentation instead of memorized tool-name or release …

    line 9
  2. Very specific:

    Use native context/compaction/session interfaces where available.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Platform Awareness

Use the current host's tool discovery, help, settings inspection, and official documentation instead of memorized tool-name or release tables. Discover deferred tools before invoking them and distinguish the client, harness, model, policy, stable/preview status, and actually available capability.

Compatibility exceptions

The historical platform notes are reference material, not current defaults. The old skill-resolver issue was closed; do not automatically disable a resolver or change user settings. Reproduce a failure in a fresh packaged-skill session before recommending a scoped workaround, and obtain settings-write consent.

A loaded skill is not evidence that its instructions were followed. A documented native feature is not runtime parity. Report unavailable capabilities and retain a tested fallback. Do not hardcode model choices or infer that a failed lookup proves retirement.

Use native context/compaction/session interfaces where available. Claim measured token or latency savings only from the actual loader/runtime, not source-file line counts.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.

Check your setup, free