knowledge-base
Skill1 starsChanged 3 months agoGPL-3.0View on GitHub
Operate a Codex-native Markdown and Obsidian personal knowledge base. Use when the user asks to remember, save, absorb, clip, organize, connect, retrieve, cite, summarize, maintain, or audit durable knowledge in a vault, including URLs, files, fragments, research findings, decisions, projects, and reusable insights.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- shetengteng/skillix-hubtheir own version, first seen Nov 8, 2026
- ITch8/customs-data-skillstheir own version, first seen Nov 8, 2026
- theopenco/llmgatewaytheir own version, first seen Nov 6, 2026
- digitalgym/aipathway-standardstheir own version, first seen Nov 4, 2026
- shinpr/rashomontheir own version, first seen Nov 1, 2026
- jjmrocha/coding-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use playwright, create-skill and 2 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.
OpenAISkillplaywright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
Also in 3 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 3 projects that use this
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- rommapp/romm★ 14ksame name
- wonderwhy-er/DesktopCommanderMCP★ 10ksame name
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- theopenco/llmgateway★ 1.7ksame name
- icey1287/SuperMew★ 884same name
- Karanjot786/TermUI★ 238same name
- JKHeadley/instar★ 86same name
- svy04/ballast★ 73same name
- zeroclaw-labs/zeroclaw-skills★ 65same name
22 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 repository21 other files it gives its agents.
- image-gen-rightcodesSkill
- image-ocrSkill
- llm-wiki-initSkill
- local-audio-transcriberSkill
- subtitle-proofreaderSkill
- video-downloaderSkill
- baoyu-translateSkill
- baoyu-format-markdownSkill
- baoyu-markdown-to-htmlSkill
- skill-lifecycleSkill
- storyweaveSkill
- check-ai-writeSkill
- correct-wrong-wordsSkill
- paper-rewriteSkill
- agent-dispatchSkill
- code-reviewerSkill
- codexSkill
- docs-writerSkill
- geminiSkill
- glm-eyesSkill
- opencodeSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
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 24 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.
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
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.