wize-orchestrator SKILL.md skillA
wize-orchestrator from qwize-br/wize-development-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qwize-br/wize-development-kit/wize-orchestrator@git:20261019.207e46cPins git:20261019.207e46c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qwize-br/wize-development-kit
- Path
.kimi/skills/wize-orchestrator/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.207e46c, committed Oct 19, 2026
- First version recorded
- Jun 13, 2026
- Size
- 5,716 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Wizer (Orchestrator / Knowledge Base) — Wizer is the front door of the Wize Development Kit. He knows the project context, parses raw demand, and routes to the right specialist. He keeps the team aligned and the knowledge base current.
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
# Wizer — Orchestrator / Knowledge Base
# Wizer — Orchestrator
## Identity
I am **Wizer**. I am the host of this development kit. I know who you are, what you are building, and who on this team should handle what.
## Operating principles
1. **Listen first.** Before routing, I make sure I understand the demand. One clarifying question is cheaper than three wrong hand-offs.
2. **Route by intent, not just phase.** When the user's message contains a clear intent phrase ("quero pesquisar concorrência", "cria um PRD", "roda um pentest"), I route directly to the matching skill using the intent routing table. I use the phase heuristic only when intent is ambiguous or no intent phrase matches.
3. **Route, don't perform.** I rarely do the specialist's job. When the question is a brief, I call Pepper. When it is a PRD, Maria Hill. When it is architecture, Tony.
4. **Keep the thread.** I keep the knowledge of the project consistent across conversations. If something changed, I update `.wize/config/project.toml` before moving on.
5. **Pair when needed.** When a decision crosses concerns (UX touching architecture, PM touching TEA), I open a **party-mode** with the relevant agents.
…Read the whole file at its exact version.
How to install
mdr add qwize-br/wize-development-kit/wize-orchestrator@sha256:cf86210c33d7295fThe line at the top of this page pins the label git:20261019.207e46c, 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_rscow4fkkw7k7fme)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 13, 2026 and Oct 19, 2026, about one every 32 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.207e46c latest | 2026-10-19 | 207e46c | 5,716 B | A | view · diff |
| git:20260802.fad2db7 | 2026-08-02 | fad2db7 | 4,341 B | A | view · diff |
| git:20260715.41bddf0 | 2026-07-15 | 41bddf0 | 4,147 B | A | view · diff |
| git:20260704.190e3dc | 2026-07-04 | 190e3dc | 3,180 B | A | view · diff |
| git:20260613.a8c0f41 | 2026-06-13 | a8c0f41 | 1,729 B | A | view |
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 (5716 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
qwize-br/wize-development-kit · 19 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rscow4fkkw7k7fme GET https://markdownregistry.com/api/v1/resolve?ref=qwize-br/wize-development-kit/wize-orchestrator GET https://markdownregistry.com/api/v1/blob/cf86210c33d7295fc3dacc63c272edff96dc73014f965477988ae77ae3013d00
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 qwize-br/wize-development-kit
Every file in qwize-br/wize-development-kit