omni-explain
Explain a finding, a drift state, or the difference between two versions of a skill, in plain words, then point at the resolution Omni already offers. Use when the user asks why Omni flags something, what differs between two versions, or what a drift means.
- License 许可
- MIT
- 所属仓库
- suarja/omni
- 最近更新
- 2026-10-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- omni-explain
- description
- Explain a finding, a drift state, or the difference between two versions of a skill, in plain words, then point at the resolution Omni already offers. Use when the user asks why Omni flags something, what differs between two versions, or what a drift means.
03 SKILL.md 正文
Explaining a finding without touching a file by hand
Every finding, drift state, or version difference Omni surfaces already has a resolution built into an existing operation. This skill's job is to read both sides, say plainly what differs, and point at that resolution — never to edit a skill folder directly.
Steps
- Identify what needs explaining: a project finding, a drift state, or two skills that look alike. Ask the user which project or skill when it is not already clear from the conversation.
- Read the relevant side(s):
- A drift or an "update"/"conflict" state:
omni_drift_report { projectId }. - What a project has, managed or not:
omni_list_project_assets { projectId }. - A possible duplicate or variant:
omni_find_skill { query }— read itsidentityFindings.
- A drift or an "update"/"conflict" state:
- State the difference in plain words: what changed, on which side, since when if known. Never guess at content you have not read.
- Propose the existing resolution for that state — never a hand edit:
update: offer to apply the marketplace version (omni-project-sync's assign step).conflict: offer to capture the project's edit into the marketplace, or to take the marketplace version instead, exactly asomni-project-syncdescribes.- A duplicate/variant finding: offer to merge them via
omni-marketplace-routing/omni-lessons, whichever fits.
- Only act after the user agrees to the specific resolution; then follow that skill's own steps and the consent rule below.
Rules
- Explain drift and duplicates as facts (hashes differ, one is newer), not as blame.
- Never write a file yourself to "fix" what you explained; hand off to the operation that owns it.
Consent
<!-- Generated from packages/omni-skills/consent.md. -->
For ordinary skill changes, previously given clear approval for this exact plan counts; do not ask again. If approval is not already clear, present the plan and wait for a clear yes; no or unclear means do nothing. For approval: "omni": Approval happens in Omni for the reason returned with the preview. Tell the user in one line, then call omni_apply; it returns pending while the request waits. Call it again with the same requestId; the request does not expire. If the user approves in Omni later, omni_receipt shows the result. Route every write through Omni preview, omni_apply, and its receipt.
For sharing or publishing, follow omni-share; author and fix skills only in the active workshop, never in a storefront.
Install external skills through Omni using omni_list_external_library, omni_preview_install_external, omni_apply and its receipt; never run npx skills add directly.
Managed files
Never edit a skill folder, a plugin or marketplace manifest, or the personal marketplace
directly — Omni's guard refuses it. Use omni_preview_update_skill, omni_preview_capture, or
omni_preview_assign to plan the change, then omni_apply using the user's existing clear authorization for that exact change.
04 同仓库更多 Skills
review
暂无简介
omni-summarize
Summarize what an agent session did, or what a receipt changed, in one factual paragraph. Use when the user asks what an agent session did, or what a receipt changed.
omni-suggest
Suggest marketplace skills that fit this project's detected stack, add the chosen ones through Omni with consent, then offer to assign them to the project. Use when the user asks what skills would help this project, what to install, or how to improve the agent setup.
omni-skill-authoring
Create or update a skill in the user's Omni marketplace through the Omni MCP tools instead of writing SKILL.md files by hand. Use when the user asks to create, write, add, improve or update a skill, or to turn a lesson into a skill.
omni-share
Share a workshop plugin through a public storefront using Omni. Use when the user says "share this plugin", "share this skill", "publish", "make a marketplace for a person, team or vertical", "lead magnet", or "storefront".
omni-project-sync
Assign marketplace skills to projects, detect drift between a project's copies and the marketplace, and resolve it through Omni's previewed operations. Use when the user asks to install, add, sync, update or check skills in a project, or when a project's skills look out of date.