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 649–672 of 28,085 skills

Mcplab Tool Interface Contracts Schema Changes 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: tool-interface contracts for schema changes. Produce a scoped risk-and-control review 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 review names relevant hazards, per...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for schema changes. Produce a scope-and-baseline record 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 owner, constraints, baseline, and acceptance signal are explicit. Use per...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts for schema changes. Produce a reviewable requirements and decision brief 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 requirements have priorities, evidence, owners, and meas...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for schema changes. Produce an evidence-backed option-comparison matrix 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 options are compared on user-approved criteria with uncerta...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for schema changes. Produce a failure-triage record and reversible recovery plan 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 failure is bounded by observations, one te...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Schema Changes Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts 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 w...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Verification And Acceptance Test PlanAUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: tool-interface contracts 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...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Source Research And Provenance LedgerAUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts 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 limitat...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts 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 e...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts 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, ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts 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 crite...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts 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 obse...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 ...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Remote Deployment Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts 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, r...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts 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 explici...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts 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...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts 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 wi...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Failure Triage And RecoveryAUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts 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 observatio...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Design BlueprintAUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 testab...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Release Readiness Build Configuration RunbookAUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts 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, reviewa...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Reconnect Handling Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts 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 ex...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Reconnect Handling Requirements And Decision BriefAUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts 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, o...securityrustgoVotes: 0GitHub stars: 2
Mcplab Tool Interface Contracts Reconnect Handling Option Comparison MatrixAUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts 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 criter...securityrustgoVotes: 0GitHub stars: 2