agentleFS
xdit-projectxdit-project/xDiT/.github/skills/documentation/SKILL.md

documentation

Skill2.8k starsChanged 10 days agoApache-2.0View on GitHub

Update xDiT docs, examples, navigation, and diagrams against current source.

118 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 2 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 4 mentionsOct 2026: 2 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the xdit-project/xDiT repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about xdit-project/xDiT

The biggest 5 of 31 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 31

Talked about on GitHub and Bluesky (31 times).

On GitHub · 30

25 more on GitHub

Used with

Projects with it also use create-media-pack, project-preferences and 10 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.
  • DepressionCenterSkill

    create-media-pack

    Create a coordinated project branding and media pack with three accessible design options, approved vector artwork, image exports, a branding guide, and README integration. Use when asked for a repository media pack, brand kit, or complete project visual identity.

    Also in 5 projects that use this

  • DepressionCenterSkill

    project-preferences

    Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

    Also in 6 projects that use this

  • thistleknotSkill

    response-style

    Response and prose protocol. Use when drafting user-facing prose, expanding a user's ideas, or tuning tone and format to preserve voice, avoid AI cliches, and maintain coherent answers.

    Also in 7 projects that use this

  • BrowserWorksSkill

    accessibility-frontend-review

    Performs an accessibility code review of a local diff or Phabricator revision in the style of the Firefox accessibility team. Use this skill whenever the user asks to review a Phabricator patch or revision for accessibility issues, mentions a D-number (like D284142) in the context of accessibility review, asks "does this patch have any a11y issues", or wants to check a diff against accessibility guidelines. Also use it when the user says things like "can you review this for a11y", "check this patch", or "give me an accessibility review of D[number]". Invoke proactively when the user pastes a phabricator.services.mozilla.com URL or shares a revision ID alongside any accessibility concern. Invoke when questions about the following topics are raised: aria properties, aria roles, high contrast mode, forced colors, prefers contrast, focus order, screen readers, assistive technology.

    Also in 4 projects that use this

  • BrowserWorksSkill

    android-new-module

    Guide for creating new Android gradle modules in the android-components project.

    Also in 4 projects that use this

  • +7 more from BrowserWorks
  • Other versions118 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 118

    1. anthropics/knowledge-work-plugins★ 36ksame name
    2. comet-ml/opik★ 23ksame name
    3. mozilla-firefox/firefox★ 14ksame name
    4. microsoft/fast★ 9.7ksame name
    5. mufeedvh/code2prompt★ 7.8ksame name
    6. BrowserWorks/waterfox★ 6.4ksame name
    7. samchon/typia★ 6ksame name
    8. github/gh-aw★ 5.6ksame name
    9. epicenter-md/epicenter★ 4.8ksame name
    10. EpicenterHQ/epicenter★ 4.8ksame name

    108 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 106 edited versions we read keep these.

  • 7

    Distinctive

    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 clear technical English inspired by ASD-STE100, without claiming formal compliance.

    line 8
  2. Distinctive:

    Verify flags and features against the parser, adapters, backend specs, and execution.

    line 11
  3. Distinctive:

    Check input/output metadata and the manual attention table against source.

    line 16
  4. Distinctive:

    Use short, active sentences, consistent terms, and exact identifiers.

    line 19
  5. Distinctive:

    Put prerequisites first and link to detail instead of repeating it.

    line 20
  6. Distinctive:

    Update paired translations and check their links.

    line 24
  7. Very specific:

    Run pre-commit run pymarkdown --all-files and python -m mkdocs build --strict.

    line 27
  8. Distinctive:

    Check links, search, archives, and desktop/mobile layouts.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 106 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

xDiT documentation

Use clear technical English inspired by ASD-STE100, without claiming formal compliance.

  • Verify flags and features against the parser, adapters, backend specs, and execution. Parser acceptance does not establish support.
  • State inputs, defaults, dependencies, hardware, and restrictions. Check each example's model, flags, and process count. Label legacy interfaces.
  • Regenerate CLI and model tables with scripts/docs/; do not edit generated pages. Check input/output metadata and the manual attention table against source.
  • Preserve external sources' titles and verify dates. Keep descriptions factual. Distinguish published images from local container builds.
  • Use short, active sentences, consistent terms, and exact identifiers. Put prerequisites first and link to detail instead of repeating it.
  • Organize pages around user tasks. Keep general guidance vendor-neutral. Exclude edit history and review conversations.
  • Archive retired guides and measurements in docs/archive/. Update paired translations and check their links.
  • Preserve the official logo. Render accessible SVGs in both themes; check execution, text alignment, padding, and arrows.
  • Run pre-commit run pymarkdown --all-files and python -m mkdocs build --strict. Check links, search, archives, and desktop/mobile layouts. Keep flags intact and tables scrolling within the page.

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.