no-os-project-readme
Skill1.4k starsChanged 8 days agoLicence not identifiedView on GitHub
Write or update a no-OS project README.rst following the repo's standard structure and the current CMake/no_os_build.py build conventions. Use when creating documentation for a project under projects/<name>/, updating an existing project README, or aligning a README with the CMake build-guide cross-linking conventions.
Trending
Quiet this year.thin dataabout the whole repository
Who's talking about analogdevicesinc/no-OS
- lvgl/lvgl“fix(makefile): Add class, instance and xml”GitHub · May 12, 2025
- analogdevicesinc/hdl“projects/ad9656_fmc: New trans. params”GitHub · Mar 21, 2025
- zephyrproject-rtos/zephyr“drivers: dac: ltc268x Zephyr driver”GitHub · Oct 16, 2024
- Nuand/bladeRF“Compile error in function `bladerf_get_gain_calibration`”GitHub · Aug 9, 2024
- enjoy-digital/litex_m2sdr“Switch to upstream AD9361 No-OS code.”GitHub · May 22, 2024
The biggest 5 of 11 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 11
Talked about on GitHub (11 times).
On GitHub · 11
- May 12, 2025fix(makefile): Add class, instance and xml — lvgl/lvgl0 reactions · 1 comment
- Mar 21, 2025projects/ad9656_fmc: New trans. params — analogdevicesinc/hdl0 reactions
- Oct 16, 2024drivers: dac: ltc268x Zephyr driver — zephyrproject-rtos/zephyr0 reactions · 2 comments
- Aug 9, 2024Compile error in function `bladerf_get_gain_calibration` — Nuand/bladeRF0 reactions · 1 comment
- May 22, 2024Switch to upstream AD9361 No-OS code. — enjoy-digital/litex_m2sdr0 reactions · 2 comments
6 more on GitHub
- May 20, 2023ADXL372 Reset at initialization too long — zephyrproject-rtos/zephyr0 reactions · 5 comments
- Mar 28, 2022Add example for ADXL355 for No-OS — analogdevicesinc/pyadi-iio0 reactions · 1 comment
- Feb 4, 2022dac_fmc_ebz_vcu118: Initial commit — analogdevicesinc/hdl0 reactions
- Apr 13, 2021ci: remove TravisCI dependencies — analogdevicesinc/EVAL-ADICUP30290 reactions
- Mar 16, 2021compat.h: Define ssize_t for ARM Compiler. — analogdevicesinc/libtinyiiod0 reactions
- Oct 13, 2015create test pattern in hardware and use the core to drive the HDMI output on the ZED board — edwardcapstone/ProjectFreeToSee0 reactions · 1 comment
In this repository3 other files it gives its agents.
- no-os-contributeSkill
- no-os-driver-readmeSkill
- no-os-source-headerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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.

