documentation
Skill15 starsChanged 23 days agoGPL-3.0View on GitHub
Use this skill to survey and catalog an Itential platform — when someone wants to know what's on their platform, document global assets (workflows, templates, LCM models, golden config, OM automations) that are NOT inside a named project, group them into logical use cases, and produce a master catalog or README. Trigger it for phrases like "document everything on the platform", "what use cases do we have?", "catalog all our global workflows", "I inherited this platform and have no idea what's there", "group our automations by use case", or "produce a platform README". The output is a structured catalog — customer-spec.md + solution-design.md per use case + master README. NOT for documenting a specific named project — use /project-to-spec for that. NOT for building new automation.
We split this skill into the rules it gives an agent
28 rules. 0 are common, 21 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 94 edited versions we read keep these.
21
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 94 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.
Other versions103 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 103
- anthropics/knowledge-work-plugins★ 34ksame name
- comet-ml/opik★ 23ksame name
- mozilla-firefox/firefox★ 14ksame name
- microsoft/fast★ 9.7ksame name
- mufeedvh/code2prompt★ 7.7ksame name
- BrowserWorks/waterfox★ 6.4ksame name
- samchon/typia★ 5.9ksame name
- github/gh-aw★ 5.5ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
93 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.
Used alongsideProjects with it also use project-preferences, response-style 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.
DepressionCenterSkillproject-preferences
Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.
Also in 4 projects that use this
- DepressionCenterSkill
response-style
Write prose in plain, natural English. Apply to every response, design discussion, review comment, commit message, pull request, and document, in any task.
Also in 4 projects that use this
BrowserWorksSkillaccessibility-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
- +8 more from BrowserWorks
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/builder-agent/assets/AGENTS.mdAGENTS.md
- skills/documentation/assets/AGENTS.mdAGENTS.md
- skills/explore/assets/AGENTS.mdAGENTS.md
- skills/gateway4-to-gateway5/assets/AGENTS.mdAGENTS.md
- skills/iag/assets/AGENTS.mdAGENTS.md
- skills/itential-mop/assets/AGENTS.mdAGENTS.md
- skills/project-to-spec/assets/AGENTS.mdAGENTS.md
- skills/qa-agent/assets/AGENTS.mdAGENTS.md
- skills/solution-arch-agent/assets/AGENTS.mdAGENTS.md
- skills/spec-agent/assets/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- builder-agentSkill
- exploreSkill
- flowagentSkill
- flowagent-to-specSkill
- gateway4-to-gateway5Skill
- iagSkill
- itential-devicesSkill
- itential-golden-configSkill
- itential-inventorySkill
- itential-json-formsSkill
- itential-lcmSkill
- itential-mopSkill
- project-to-specSkill
- qa-agentSkill
- solution-arch-agentSkill
- spec-agentSkill
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.