Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

verify-local-config-before-claims

Étoiles0

Forks0

Mis à jour8 février 2026 à 06:39

Verify repository configuration locally before making conclusions about MCP/server setup. Use when asked to diagnose configuration, profile routing, auth behavior, endpoints, env vars, or profile IDs/aliases in this workspace.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

davidruzicka

davidruzicka/mcp4openapi

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	verify-local-config-before-claims
description	Verify repository configuration locally before making conclusions about MCP/server setup. Use when asked to diagnose configuration, profile routing, auth behavior, endpoints, env vars, or profile IDs/aliases in this workspace.

Verify Local Config Before Claims

Inspect local source of truth before answering.

Read relevant profile files under profiles/.
Check transport and auth behavior in src/transport/http-transport.ts and related docs.
Verify route format and profile selection from README.md and docs/HTTP-TRANSPORT.md.

Confirm claims with concrete evidence.

Cite exact file paths and key values (profile id, aliases, auth type, env var names, endpoint paths).
Prefer direct file reads over memory or assumptions.

Distinguish static config from runtime prerequisites.

State whether config syntax is valid.
Separately list runtime conditions required for it to work (enabled transport mode, env vars set, profile routing on).

Resolve conflicts explicitly.

If docs and code differ, prioritize code and note the discrepancy.
If multiple profiles exist, identify which one matches the user snippet.

Avoid speculative diagnoses.

Do not claim a field is wrong unless a local check confirms it.
When unsure, run one more targeted file check before concluding.

Plus depuis ce dépôt

même dépôt

auto-update-skills

davidruzicka/mcp4openapi

After correction/feedback: propose new skill or update existing to capture reusable pattern. Covers knowledge, tools, policies, preferred style. Trigger immediately for critical issues, on repetition for trivial patterns.

2026-04-280

prepare-release-publishing

davidruzicka/mcp4openapi

Prepare patch/minor/major release publishing in this repository by inserting a dated version header under `## [Unreleased]` in `CHANGELOG.md`, bumping `package.json` with `npm version`, and verifying both files are consistent. Use when asked with prompts like "prepare patch publishing", "prepare minor release", or "prepare major publish".

2026-02-250

create-crud-mcp-profile

davidruzicka/mcp4openapi

Create a new CRUD MCP profile from an OpenAPI spec in this repository. Use when a user asks for a profile equivalent to existing CRUD-style profiles (for example YouTrack, Grafana, GitLab, GitHub Security), including action mapping, parameter modeling, profile tests, docs updates, and validation.

2026-02-220

review-plan-before-implementation

davidruzicka/mcp4openapi

Run an interactive pre-implementation plan review with explicit tradeoffs, opinionated recommendations, and user checkpoints before any code changes. Use when asked to review a plan, challenge architecture, assess quality/testing/performance risks, or decide implementation direction.

2026-02-190

use-correct-github-review-comment-enums

davidruzicka/mcp4openapi

Enforce schema-correct enum values when posting GitHub PR review comments via MCP tools. Use when creating inline review comments or handling tool validation errors for review-thread parameters.

2026-02-190

codex-mcp-config-format-matrix

davidruzicka/mcp4openapi

Use when generating or reviewing MCP configuration snippets for Codex (CLI/TOML) to enforce Codex-native auth and format rules.

2026-02-150

name	verify-local-config-before-claims
description	Verify repository configuration locally before making conclusions about MCP/server setup. Use when asked to diagnose configuration, profile routing, auth behavior, endpoints, env vars, or profile IDs/aliases in this workspace.

Verify Local Config Before Claims

Inspect local source of truth before answering.

Read relevant profile files under profiles/.
Check transport and auth behavior in src/transport/http-transport.ts and related docs.
Verify route format and profile selection from README.md and docs/HTTP-TRANSPORT.md.

Confirm claims with concrete evidence.

Cite exact file paths and key values (profile id, aliases, auth type, env var names, endpoint paths).
Prefer direct file reads over memory or assumptions.

Distinguish static config from runtime prerequisites.

State whether config syntax is valid.
Separately list runtime conditions required for it to work (enabled transport mode, env vars set, profile routing on).

Resolve conflicts explicitly.

If docs and code differ, prioritize code and note the discrepancy.
If multiple profiles exist, identify which one matches the user snippet.

Avoid speculative diagnoses.

Do not claim a field is wrong unless a local check confirms it.
When unsure, run one more targeted file check before concluding.