desktop-security-update SKILL.md skillA
desktop-security-update from lobehub/lobehub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lobehub/lobehub/desktop-security-update@git:20261012.6f8af58Pins git:20261012.6f8af58 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lobehub/lobehub
- Path
.agents/skills/desktop-security-update/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261012.6f8af58, committed Oct 12, 2026
- Size
- 6,191 bytes
- Repository stars
- 84,260
- License
- a license file GitHub does not identify
Inspect, mark, or revoke vulnerable LobeHub Desktop versions through the existing release workflow and signed R2 security policy. Use for forced security updates across Stable, Canary, Beta, and Nightly.
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
# Desktop security updates Operate `.github/workflows/release-desktop-core-ota.yml` using its `security_policy` input. This selects only the policy job; it does not build or publish Core. The policy is global across channels at `<UPDATE_SERVER_URL base>/security-policy.json` in the existing update bucket. Read [the policy contract](../../../apps/desktop/docs/security-updates.md) for client behavior and delivery limitations. The deterministic operator is `apps/desktop/scripts/desktopSecurityPolicy.mjs`; it shares schema/signature validation with the client. Do not hand-sign JSON, fetch signing secrets locally, replace the whole rule set, or add a workflow. ## Resolve the request For a mark, determine the installer build channel, platforms, `shell` or `core` target, affected npm SemVer range, fixed full-installer version, and reason. An exact version is a valid range. Do not guess the affected scope from the latest release. If scope is ambiguous, inspect the current policy while asking only for the missing scope. Publish the fixed installer first: the operator checks the public feed and installer availability for every requested platform, including both macOS architectures. Beta …
Read the whole file at its exact version.
How to install
mdr add lobehub/lobehub/desktop-security-update@sha256:5ae6a6130165ae42The line at the top of this page pins the label git:20261012.6f8af58, 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_6t667sfdhaafcpvy)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 12, 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 (6191 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
lobehub/lobehub · 84,260 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch canary
API
GET https://markdownregistry.com/api/v1/artifacts/art_6t667sfdhaafcpvy GET https://markdownregistry.com/api/v1/resolve?ref=lobehub/lobehub/desktop-security-update GET https://markdownregistry.com/api/v1/blob/5ae6a6130165ae426ed3caefe6082c4cfd1e6d9765f6901e8687af5b89441599
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.