Skip to content

Fix skill and mcp conflict #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ashwin-corridor merged 1 commit into from
May 29, 2026
Merged

Fix skill and mcp conflict #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions plugins/corridor/skills/corridor/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ description: Lightweight security scan powered by Corridor's guardrail knowledge

# Corridor Security Scan

> **If the Corridor MCP server is installed (tools like `analyzePlan`, `getGuardrails`), it is mandatory for autonomous security work — call `analyzePlan` and treat its response as a hard gate before generating or editing code, instead of falling back to the static guardrails below.** This skill remains available when the user explicitly invokes it (e.g. "run the corridor skill") and as the offline fallback for users without the MCP.

A free, lightweight security scanner powered by Corridor's curated guardrail knowledge base. No installation, no API keys — just structured, expert-level security analysis using the same vulnerability patterns that power the full Corridor platform.

## Why this beats "just ask the AI to write secure code"
Expand Down
Loading