Security

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

skills in category: 28,085
pages available: 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 browser

Browse security skills

Showing 817–840 of 28,085 skills

Mcplab Server Registry Metadata Reconnect Handling Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: server-registry metadata for reconnect handling. Produce a bounded build or configuration runbook 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 prepared result is reproducible, re...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability 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: server-registry metadata for observability. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means the review names relevant hazards, per...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use per...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means requirements have priorities, evidence, owners, and meas...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means options are compared on user-approved criteria with uncerta...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means the failure is bounded by observations, one te...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means interfaces, dependencies, constraints, and review points are testable before ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Observability Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: server-registry metadata for observability. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means the prepared result is reproducible, reviewable, and w...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Local Development 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: server-registry metadata for local development. Produce a scoped risk-and-control review 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 review names relevant hazards,...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Local Development Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: server-registry metadata for local development. Produce a scope-and-baseline record 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 owner, constraints, baseline, and acceptance signal are explicit. Use...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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 ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Local Development Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: server-registry metadata 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 unc...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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, on...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Local Development Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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 bef...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Local Development Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: server-registry metadata 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, a...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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. ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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, a...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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 ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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,...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Least Privilege Access Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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 ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 exp...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata 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: server-registry metadata 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, ow...securityrustgoVotes: 0GitHub stars: 2
Mcplab Server Registry Metadata Conformance Testing Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: server-registry metadata 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 criteri...securityrustgoVotes: 0GitHub stars: 2