agentleFS
frankxaifrankxai/awesome-motion-design-agent-skills/.github/copilot-instructions.md

awesome-motion-design-agent-skills

Copilot instructions111 starsChanged 11 days agoCC0-1.0View on GitHub

Public, CC0, web-first curated list plus installable Agent Skills (skills/*/SKILL.md).

The file

We split this copilot-instructions.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Never add private paths, credentials, internal strategy, affiliate links, or unverified tools.

    line 6
  2. Distinctive:

    Every catalog entry: primary URL, one-sentence distinct value, license, dated pulse.

    line 7
  3. Very specific:

    Keep <!-- fleet:*:start/end --> blocks untouched — they are synced from the fleet control plane.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions 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
copilot-instructions.md

Copilot instructions — awesome-motion-design-agent-skills

Public, CC0, web-first curated list plus installable Agent Skills (skills/*/SKILL.md).

  • Scope for Copilot: link rot, metadata pulses (stars/license/archived via GitHub API), frontmatter fixes, Dependabot/Actions bumps. Editorial additions and skill rewrites go to a human-reviewed PR.
  • Never add private paths, credentials, internal strategy, affiliate links, or unverified tools. skills-validate fails on local paths.
  • Every catalog entry: primary URL, one-sentence distinct value, license, dated pulse. Curate aggressively; no link dumps.
  • Keep <!-- fleet:*:start/end --> blocks untouched — they are synced from the fleet control plane.
  • Skill folder name == frontmatter name, kebab-case; description says when it fires, ≤1024 chars.
  • A PR is done when Link Checker and Skills Validate are green. Keep PRs single-purpose; no WIP drafts left open >72h.

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.