agent-notes SKILL.md skillA
agent-notes from cherryhq/cherry-studio is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cherryhq/cherry-studio/agent-notes@git:20261017.46ef0b8Pins git:20261017.46ef0b8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cherryhq/cherry-studio
- Path
.agents/skills/agent-notes/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261017.46ef0b8, committed Oct 17, 2026
- Size
- 4,600 bytes
- Repository stars
- 52,815
- License
- AGPL-3.0
Use when deciding whether a Cherry Studio change needs an Agent Note, authoring or reviewing a Spec, recording a durable bug-fix decision, moving a note between proposed/implemented/rejected, or checking supersession and stacked Spec approval.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Agent Notes Read [the Agent Note rules](../../notes/README.md) before acting. Agent Notes preserve revisitable decisions; they do not replace current code, reference docs, issues, or PR discussion. ## Classify the change Every human-authored PR declares an Agent Note or an explicit `N/A` reason. Automation-authored PRs (repository workflows and Dependabot) are exempt from this metadata requirement, not from normal validation. The class names the decision's subject; it does not force every note to start as proposed. Choose the initial lifecycle from whether the target needs human agreement before implementation and whether the decision has already shipped. - Use `N/A` for a local or mechanical edit that restores an existing contract without a durable tradeoff. - Write an implemented `bug-fix` note in the same PR when the repair changes failure, compatibility, security, concurrency, atomicity, lifecycle, or another choice likely to be reversed without its root cause. - A small, completed testing or other durable decision that does not meet the Spec-first threshold may enter its owning class as implemented. …
Read the whole file at its exact version.
How to install
mdr add cherryhq/cherry-studio/agent-notes@sha256:e6c1959b86beffadThe line at the top of this page pins the label git:20261017.46ef0b8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_o7z3224yuzhtklav)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 17, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4600 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cherryhq/cherry-studio · 52,815 stars · license AGPL-3.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o7z3224yuzhtklav GET https://markdownregistry.com/api/v1/resolve?ref=cherryhq/cherry-studio/agent-notes GET https://markdownregistry.com/api/v1/blob/e6c1959b86beffadfc9a880b3970f9d6f6bda9efc94e7be939a9d1b4c04cd345
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from cherryhq/cherry-studio
Every file in cherryhq/cherry-studio