mcpv

Name: mcpv
Author: wibus-wee

This file provides guidance to code when working with code in this repository.

by wibus-wee(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from wibus-wee/mcpv (AGENTS.md). Install upstream with npx skills add wibus-wee/mcpv. Copyright stays with the author.

AGENTS.md

This file provides guidance to code when working with code in this repository.

ExecPlans

When writing complex features or significant refactors, use an ExecPlan (as described in .agents/PLANS.md) from design to implementation. If you write an ExecPlan, save the file into the docs/EXEC_PLANS directory.

You Need To

Plan Mode: You need to first understand the source code and identify which Skills you need to utilize.
Code Mode: You should actively call various Skills to accomplish the task.
After Code Mode: You should run make lint-fix to fix linting issues and make test to run tests before submitting.

Additional AGENTS.md Files

if there is AGENTS.md/CLAUDE.md in subdirectories, please also follow the guidelines described in those files.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Installed into a catalogue, chosen by a router

Install mcpv and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

wibus-wee-mcpv-mcpv.ocm.jsonjson

{
  "ocm": "1",
  "id": "wibus-wee-mcpv-mcpv",
  "kind": "skill",
  "name": "mcpv",
  "description": "This file provides guidance to code when working with code in this repository.",
  "publisher": "wibus-wee",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github-agents"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "This file provides guidance to code when working with code in this repository."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-agents",
      "repository": "https://github.com/wibus-wee/mcpv",
      "path": "AGENTS.md",
      "ref": "8d2f707aec1a079c486bddb3bcf56240369ed8e2",
      "url": "https://github.com/wibus-wee/mcpv/blob/8d2f707aec1a079c486bddb3bcf56240369ed8e2/AGENTS.md",
      "key": "wibus-wee/mcpv/AGENTS.md"
    }
  },
  "instructions": "# AGENTS.md\n\nThis file provides guidance to code when working with code in this repository.\n\n## ExecPlans\n\nWhen writing complex features or significant refactors, use an ExecPlan (as described in .agents/PLANS.md) from design to implementation. If you write an ExecPlan, save the file into the `docs/EXEC_PLANS` directory.\n\n## You Need To\n\n- Plan Mode: You need to first understand the source code and identify which Skills you need to utilize.\n- Code Mode: You should actively call various Skills to accomplish the task.\n- After Code Mode: You should run `make lint-fix` to fix linting issues and `m",
  "cost": {
    "context_tokens": 196
  }
}

Fetch it by URL: GET /api/v1/registry/wibus-wee-mcpv-mcpv/manifest?version=1.0.0