Skip to content
Back to skills

Mhproto Discover

ASecurity

Discover a capability in an existing app and produce source-backed MHProto behaviour, interface and example drafts. Use for adopting MHProto or inspecting a capability before specification work.

  • 4 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 4, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add rbsx/mhproto --skill mhproto-discover --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mhproto Discover?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mhproto Discover
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rbsx-mhproto-discover/badge)](https://www.skillsdirectory.com/skills/rbsx-mhproto-discover)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mhproto-discover
description: Discover a capability in an existing app and produce source-backed MHProto behaviour, interface and example drafts. Use for adopting MHProto or inspecting a capability before specification work.
---

# MHProto Discover

Start with `mhproto context` for the feature index, then `mhproto context --capability ID --operation ID` for the affected endpoint (or `--entity KIND:ID` for other interface entities). Load only relevant `--rule`, `--schema`, `--example` or `--check` detail; `--section` narrows a packet. Read every deferred rule group the change touches before editing. Inspect the authoritative source when deciding intent or making a change. Do not load the exported HTML or whole `mhproto inspect` model into the prompt. Visual packets contain references; open images/design links only when needed.

Read the project’s AGENTS.md and authoritative product docs, then mhproto.yaml and the relevant capability. Inspect providers, consumers, existing schemas and tests. Reuse an existing OpenAPI 3.1 interface or its generator; do not invent a parallel schema.

Record behaviour as confirmed, inferred or unknown with source paths. Preserve existing approval provenance. Reverse-engineered code describes observations; it does not approve requirements. Surface disagreements with product docs. Bound discovery to the requested capability.

Write small capability drafts, numbered rules and representative examples, including a failure/recovery case. Leave missing checks and unknown decisions visible. Read ../mhproto-format/SKILL.md for the file model. Run `mhproto check` after changes. Do not alter application behaviour as part of discovery.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.