Hermes Imports
affaan-m/ECC
将本地 Hermes 操作员工作流转换为经过清理的 ECC 技能和发布包工件。在准备将 Hermes 工作流用于公共 ECC 重用而不泄露私有工作区状态、凭据或仅本地路径时使用。
Update SenseNova Skills (the sn- bundle) inside an OpenClaw or hermes-agent install.
MITAuto-check passed
Install Sn Update
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sn-update .claude/skills/sn-update && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .claude/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sn-update .agents/skills/sn-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .agents/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sn-update .cursor/skills/sn-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .cursor/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenSenseNova/SenseNova-Skills.git --path skills/sn-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sn-update .gemini/skills/sn-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .gemini/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sn-update .github/skills/sn-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .github/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenSenseNova/SenseNova-Skills sn-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenSenseNova/SenseNova-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sn-update .opencode/skills/sn-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sn-update" agent skill from https://github.com/OpenSenseNova/SenseNova-Skills/tree/main/skills/sn-update into .opencode/skills/sn-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sn-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sn-update- GitHub stars
- 5.7k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 613 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
Update SenseNova Skills (the sn- bundle) inside an OpenClaw or hermes-agent install.
- Works in 3 steps: Move (not copy) any existing // into a → Copy /skills// → //. → Write .sn-version with the upstream…
- The user says any of: update SenseNova skills
- SKILL.md covers Decide the scope, Decide the target agent, Sync the upstream repo and Compare versions per skill (A…, plus 4 more sections
- Calls git
What it does
Sn Update is an agent skill from OpenSenseNova/SenseNova-Skills. Update SenseNova Skills (the sn- bundle) inside an OpenClaw or hermes-agent install. ALWAYS use this skill when the user says any of: "update SenseNova skills", "update SN skills", "更新 sensenova skills", "更新 sn skills", "刷新 sn-", "升级 sn- skills", or names a specific sn- skill to update (e.g. "更新 sn-ppt-standard", "refresh sn-image-base"). Default scope is the whole sn- bundle; if the user names specific skills, update ONLY those.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Modular SenseNova skills for building AI-powered office assistants and productivity workflows. The licence is MIT.
When your agent uses it
- The user says any of: update SenseNova skills
- Update SN skills
- 更新 sensenova skills
- Names a specific sn- skill to update (e.g
Example prompts
- “update SenseNova skills”
- “update SN skills”
- “更新 sensenova skills”
- “/sn-update”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Move (not copy) any existing // into a
- Copy /skills// → //.
- Write .sn-version with the upstream subtree SHA inside the new copy.
What it can do on your machine
Read from SKILL.md and the folder at commit 5abde96. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sn Update loads about 1.4k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 613 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OpenSenseNova/SenseNova-Skills at commit 5abde96, republished under its MIT licence (© OpenSenseNova). 613 words, ~1,395 tokens.
Download SKILL.mdSave it as
.claude/skills/sn-update/SKILL.md (or your agent's skills folder).- name
- sn-update
- description
- Update SenseNova Skills (the sn-* bundle) inside an OpenClaw or hermes-agent install. ALWAYS use this skill when the user says any of: "update SenseNova skills", "update SN skills", "更新 sensenova skills", "更新 sn skills", "刷新 sn-*", "升级 sn-* skills", or names a specific sn-* skill to update (e.g. "更新 sn-ppt-standard", "refresh sn-image-base"). Default scope is the whole sn-* bundle; if the user names specific skills, update ONLY those.
- metadata.project
- SenseNova-Skills
- metadata.tier
- 1
- metadata.category
- meta
- metadata.user_visible
- true
- triggers
- sn-update, 更新 sn, 更新 sensenova, update sn skills, update SN skills, 更新 sn skills, 刷新 sn-*, 刷新 sn skills, 更新 sn-ppt-standard, refresh sn-image-base, update…
sn-update
Refresh installed sn-* skills from upstream
SenseNova-Skills.
Decide the scope
- No list given → every
sn-*skill upstream. - Specific skills named → only those. Don't expand.
- A named skill missing upstream → surface as error and stop.
- User said "force / 强制" → re-install even when up-to-date.
Decide the target agent
Check which directories exist:
~/.openclaw/skills/ | ~/.hermes/skills/ | Target |
|---|---|---|
| exists | absent | openclaw |
| absent | exists | hermes |
| exists | exists | ask the user — never silently dual-write |
| absent | absent | no install found, stop |
Sync the upstream repo
Persistent cache at ~/.cache/sn-update/repo/. Default URL:
https://github.com/OpenSenseNova/SenseNova-Skills.git. User may override
with a fork URL.
- First run: if you want to actually limit blob download, use partial
clone with
--filter=blob:none --no-checkout, then sparse-checkout only the selectedskills/<name>paths before copying them.--filter=blob:nonealone does not keep the cache small if the full worktree is checked out; that checkout will still download most or all needed blobs. It still preserves history metadata for SHA queries. - Subsequent runs: fetch + hard-reset to the upstream default branch, and
re-apply sparse-checkout for only the requested
skills/<name>paths before copying. If updating the wholesn-*bundle, expect most/all skill blobs to be downloaded. - URL changed: if cache's
origindiffers from the requested URL, delete and re-clone.
Compare versions per skill (A → B → C)
For each skill, pick the highest-precedence signal present on both sides (installed + upstream); equal → skip, differ → install.
Upstream "version" is the per-subtree commit SHA — using repo HEAD would mark unrelated skills as stale every time:
git -C <cache> log -1 --format=%H -- skills/<skill-name>- A —
.sn-versionmarker: one-line file inside the installed skill holding the SHA from its last install. - B —
.sn-releasemarker (fallback): one-line file holding the upstream tag name. Compare againstgit describe --tags --abbrev=0. - C — optional
version:field in SKILL.md frontmatter: parse from YAML on both sides, but only for forks or skills that explicitly add this field. If either side lacks it, C does not apply. - Nothing usable → treat as stale and install.
Always write .sn-version on install so future runs can use A.
Show full SKILL.md (290 more words)Show less
Install with backup
For each skill flagged "install":
- Move (not copy) any existing
<agent-skills>/<skill-name>/into a single timestamped backup bucket shared by all skills in this run:~/.<agent>/skills_backup/<UTC-timestamp>/<skill-name>/(e.g.2026-04-30T15-29-07Z). - Copy
<cache>/skills/<skill-name>/→<agent-skills>/<skill-name>/. Never symlink (ln -s) from the cache. The cache lives under~/.cache/with permissions the agent runtime may not be able to traverse, and some runtimes refuse to load skills resolved through symlinks. Always do a real recursive copy so the installed tree is self-contained and owned by the agent skills dir. - Write
.sn-versionwith the upstream subtree SHA inside the new copy.
If the bucket ends up empty (all targets were fresh installs), remove it.
The backup tree is a sibling of skills/, never a .bak folder
inside it — most agent runtimes scan the whole skills/ directory and
would pick up stale duplicates.
Enforce backup retention
After every run, prune the per-agent backup root to at most 3 buckets. Timestamps sort lexicographically; keep the newest 3, delete the rest. Run this even when the current run produced no backup of its own.
Report to the user
Group by status, keep it short:
Updated (3): sn-ppt-standard, sn-image-base, sn-deep-research
Already up-to-date (5): sn-ppt-creative, sn-ppt-doctor, ...
Backup: ~/.openclaw/skills_backup/2026-04-30T15-29-07Z/- Omit
Backup:when nothing was backed up. - Show SHA pairs (
abc1234 → def5678) only if the user asks for detail. - Errors get their own line — never bury them in a success summary.
Edge cases
- Asks to delete sn- skills* — not this skill's job. Decline; point at
~/.<agent>/skills_backup/if they want to roll back. - User is in the dev repo and asks to "update sn skills" — they mean push to their agent install. Proceed normally; this skill only touches the cache and the agent install dirs, never the dev checkout.
sn-updateupdating itself — fine; the new copy takes effect on the next invocation.
© OpenSenseNova, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sn-update of OpenSenseNova/SenseNova-Skills.
Open the folder on GitHubat commit 5abde96
Compare with similar skills
Sn Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sn Update this skillOpenSenseNova/SenseNova-Skills | 5.7k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Hermes Importsaffaan-m/ECC | 275k | — | ~324 | Automated safety check: Pass | MIT | |
| Hermes Importsaffaan-m/ECC | 275k | 1 repos | ~752 | Automated safety check: Pass | MIT | |
| Inspecting Hermes Desktop DomNousResearch/hermes-agent | 252k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Hermes Tweetwshobson/agents | 40k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Hermes Imports
affaan-m/ECC
Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts.
Inspecting Hermes Desktop Dom
NousResearch/hermes-agent
Read the live Hermes desktop DOM/CSS over CDP. An agent skill from NousResearch/hermes-agent.
Hermes Tweet
wshobson/agents
Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Triage Support Bundle
netdata/netdata
Investigate a Netdata support bundle offline - the archive netdata-support-bundle produces - to explain one host's alerts, missing data, collector failures, crashes, high CPU or memory, streaming…
More from OpenSenseNova/SenseNova-Skills
All 36 skills in this repoSenseNova PPT Workbench
OpenSenseNova/SenseNova-Skills
Opens the PPT Workbench web editor for an existing SenseNova HTML slide deck so you can preview, inspect and visually edit it without regenerating.
SN Motion HTML
OpenSenseNova/SenseNova-Skills
Builds HTML stories where one continuous camera journey advances with page progress, using researched structure, AI stills, Seedance video clips and browser QA.
China Market Open Data Search
OpenSenseNova/SenseNova-Skills
Researches Chinese market, macro, trade, procurement, listed-company and regulatory information from free official sources that need no sign-up or API key.
SenseNova PPT Fallback Tools
OpenSenseNova/SenseNova-Skills
Fallback scripts for web search, image search and download, and image generation that PPT skills use only when the host agent lacks or fails its own tools.
SenseNova PPT Creative Renderer
OpenSenseNova/SenseNova-Skills
Turns an approved slide outline into a full-page image for every slide, one 16:9 PNG per page, and optionally packages the set into a PPTX.
SenseNova PPT Entry
OpenSenseNova/SenseNova-Skills
Entry point for SenseNova presentation generation: creates a task folder, picks depth, output format and design richness, and routes to the right PPT skill.
Questions about Sn Update
What does Sn Update do?
Update SenseNova Skills (the sn- bundle) inside an OpenClaw or hermes-agent install. Sn Update is an agent skill from OpenSenseNova/SenseNova-Skills. Update SenseNova Skills (the sn- bundle) inside an OpenClaw or hermes-agent install.
When should I use Sn Update?
Sn Update fits situations like: the user says any of: update SenseNova skills; update SN skills; 更新 sensenova skills; names a specific sn- skill to update (e.g.
How do I install Sn Update in Claude Code?
Run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a claude-code`. Or copy the skill folder (skills/sn-update in OpenSenseNova/SenseNova-Skills) into .claude/skills/sn-update in your project. Claude Code loads it when a task matches its description.
How do I install Sn Update in Codex?
Run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a codex`. Or copy the skill folder (skills/sn-update in OpenSenseNova/SenseNova-Skills) into .agents/skills/sn-update in your project. Codex loads it when a task matches its description.
Can I use Sn Update in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenSenseNova/SenseNova-Skills --skill sn-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sn-update, .gemini/skills/sn-update, .github/skills/sn-update and .opencode/skills/sn-update in your project.
What does Sn Update need to run?
Going by SKILL.md and its folder, Sn Update needs the command-line tools its instructions call (git).
Does Sn Update access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Sn Update safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sn Update use?
Sn Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sn Update use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sn Update?
Skills that share tags, products or a category with Sn Update: Hermes Imports (affaan-m/ECC, 275k stars), Hermes Imports (affaan-m/ECC, 275k stars), Inspecting Hermes Desktop Dom (NousResearch/hermes-agent, 252k stars) and Hermes Tweet (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sn Update?
OpenSenseNova (a GitHub organization) maintains it in OpenSenseNova/SenseNova-Skills, which has 5,747 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on September 18, 2026.
Source: OpenSenseNova/SenseNova-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.