Security

Security audits, vulnerabilities, compliance, auth, secrets, and safe automation

skills in category: 29,018
pages available: 1,210

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 browser

Browse security skills

Showing 2,065–2,088 of 29,018 skills

Mcplab Capability Negotiation Local Development Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: capability negotiation for local development. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means requirements have priorities, evidence, owners, and me...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Local Development Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation for local development. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means options are compared on user-approved criteria with uncer...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Local Development Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: capability negotiation for local development. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the failure is bounded by observations, one ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Local Development Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation for local development. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means interfaces, dependencies, constraints, and review points are testable befor...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Local Development Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation for local development. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the prepared result is reproducible, reviewable, and...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the owner, constraints, baseline, and acceptance signal are explicit. Us...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means requirements have priorities, evidence, owners, and...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means options are compared on user-approved criteria with un...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the failure is bounded by observations, o...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means interfaces, dependencies, constraints, and review points are testable be...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Least Privilege Access Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation for least-privilege access. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the prepared result is reproducible, reviewable, ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the owner, constraints, baseline, and acceptance signal are expli...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means requirements have priorities, evidence, owne...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means options are compared on user-approved criteria ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the failure is bounded by observat...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means interfaces, dependencies, constraints, and review points are test...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Conformance Testing Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation for conformance testing. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the prepared result is reproducible, revie...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Security Rights And Safety ReviewAUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the review names relevant hazards,...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means requirements have priorities, evidence, owners, and ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means options are compared on user-approved criteria with unc...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the failure is bounded by observations, on...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means interfaces, dependencies, constraints, and review points are testable bef...securityrustgoVotes: 0GitHub stars: 2
Mcplab Capability Negotiation Client Compatibility Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation for client compatibility. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the prepared result is reproducible, reviewable, a...securityrustgoVotes: 0GitHub stars: 2