Bring up an owned Yandex speaker for an agent SKILL.md skillA
Bring up an owned Yandex speaker for an agent from howdeploy/deploychan_mcp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add howdeploy/deploychan_mcp/Bring up an owned Yandex speaker for an agent@git:20261027.7bb973cPins git:20261027.7bb973c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- howdeploy/deploychan_mcp
- Path
content/skills/yandex-speaker-bringup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261027.7bb973c, committed Oct 27, 2026
- Size
- 3,430 bytes
- Repository stars
- 21
- License
- MIT
Assess and set up an owned Yandex speaker as an agent audio terminal: model/firmware compatibility, bounded root bootstrap, persistent maintenance, private backup and intentional isolation. Use for device bring-up or its recovery, not ordinary desktop commands.
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
# Speaker bring-up Use the exact user-owned target and requested features. The reference experience is Mini 1 YNDX-0004; other models require their own compatibility evidence. This skill is a procedure, not a bundled exploit/firmware installer. 1. Identify hardware label, current build, power/data connection, host OS, router control and existing access. State which functions require the PC or a provider. If connected to Deploychan MCP, retrieve `yandex-speaker-feasibility` for the matrix. 2. Read the current [community root instructions](https://hackalice.me/start/root/) and matching device page. Preserve network settings and explain any required reset. Do not update or reset an unidentified device just to see whether access appears. 3. Prepare the chosen local/scoped bootstrap and verify it is ready before directing the user to change DNS or connect the speaker. Record each original setting and corresponding undo step. Confirm real requests/access, not only service status. 4. Inspect and apply the appropriate [SSH/update procedure](https://hackalice.me/start/ssh/) within authorization. Protect maintenance access from untrusted networks and …
Read the whole file at its exact version.
How to install
mdr add howdeploy/deploychan_mcp/Bring up an owned Yandex speaker for an agent@sha256:73ad5f0aaa7c9717The line at the top of this page pins the label git:20261027.7bb973c, 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_4hmrpojolc2my7u2)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 27, 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 (3430 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
howdeploy/deploychan_mcp · 21 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4hmrpojolc2my7u2 GET https://markdownregistry.com/api/v1/resolve?ref=howdeploy/deploychan_mcp/Bring up an owned Yandex speaker for an agent GET https://markdownregistry.com/api/v1/blob/73ad5f0aaa7c97171dbb57e6622bd375687eb127ae07abb8d9f31aefb6d5d845
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.