All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 28,085
- 1,171
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse security skills
Showing 721–744 of 28,085 skills
- Mcplab Stdio Transport Schema Changes Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means interfaces, dependencies, constraints, and review points are testable before build. Us...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means the prepared result is reproducible, reviewable, and within the...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means each critical requirement maps to ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means material claims are linked to current primary sources with dates and limitations. Use...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means the review names relevant hazar...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means the owner, constraints, baseline, and acceptance signal are explicit. ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means requirements have priorities, evidence, owners, a...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means options are compared on user-approved criteria with ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means the failure is bounded by observations,...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means interfaces, dependencies, constraints, and review points are testable ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Remote Deployment Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for remote deployment. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means the prepared result is reproducible, reviewable...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the review names relevant hazards, pe...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use pe...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means requirements have priorities, evidence, owners, and mea...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means options are compared on user-approved criteria with uncert...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a versioned improvement proposal and handoff packet with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the proposed change is compar...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the failure is bounded by observations, one t...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means interfaces, dependencies, constraints, and review points are testable before...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Release Readiness Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for release readiness. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the prepared result is reproducible, reviewable, and ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Reconnect Handling Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for reconnect handling. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the review names relevant hazard...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Reconnect Handling Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for reconnect handling. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the owner, constraints, baseline, and acceptance signal are explicit. U...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Reconnect Handling Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for reconnect handling. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means requirements have priorities, evidence, owners, an...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Reconnect Handling Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for reconnect handling. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means options are compared on user-approved criteria with u...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Reconnect Handling Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for reconnect handling. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the failure is bounded by observations, ...Votes: 0GitHub stars: 2