All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Authorizedsec Cloud Identity Threat Modeling Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means the failure is bounded by observations, one...Votes: 0GitHub stars: 2
- Authorizedsec Cloud Identity Threat Modeling Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means options are compared on user-approved criteria with unce...Votes: 0GitHub stars: 2
- Authorizedsec Cloud Identity Threat Modeling Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means requirements have priorities, evidence, owners, and m...Votes: 0GitHub stars: 2
- Authorizedsec Cloud Identity Threat Modeling Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use ...Votes: 0GitHub stars: 2
- Authorizedsec Cloud Identity Threat Modeling Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means material claims are linked to current primary sources with dates and limitations. Use per...Votes: 0GitHub stars: 2
- Authorizedsec Cloud Identity Threat Modeling Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Authorized cybersecurity testing and defense: cloud identity for threat modeling. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means each critical requirement maps to a re...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means the prepared result is reproducible, reviewab...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means interfaces, dependencies, constraints, and review points are testabl...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means the failure is bounded by observation...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means options are compared on user-approved criteria wit...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means requirements have priorities, evidence, owners,...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means the owner, constraints, baseline, and acceptance signal are explicit...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Authorized Lab Verification Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: container hardening for authorized lab verification. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Reproduce only in a deliberately isolated lab or owner-approved safe fixture, using benign payloads and synthetic data. Success means material claims are linked to current primary sources with dates and limitations. U...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the prepared result is reproducible, reviewable, and within the approved...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permiss...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the failure is bounded by observations, one testable hypothesis,...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for change impact. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means options are compared on user-approved criteria with uncertainty and trade-off...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means requirements have priorities, evidence, owners, and measurable acceptance ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the review names relevant hazards, permissions, controls...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, pre...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means each critical requirement maps to a reproducible check and ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the prepared result is reproducible, reviewable, and within the appro...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means interfaces, dependencies, constraints, and review points are testable before build. Use perm...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the failure is bounded by observations, one testable hypothes...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means options are compared on user-approved criteria with uncertainty and trade-...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means requirements have priorities, evidence, owners, and measurable acceptan...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned input...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means the review names relevant hazards, permissions, contr...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Control Coverage Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Authorized cybersecurity testing and defense: container hardening for control coverage. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Tie each claimed safeguard to an observable requirement/test and name any control that remains unverified. Success means each critical requirement maps to a reproducible check a...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means the prepared result is reproducible, reviewa...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means interfaces, dependencies, constraints, and review points are testab...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means the failure is bounded by observatio...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means options are compared on user-approved criteria wi...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means requirements have priorities, evidence, owners...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means the owner, constraints, baseline, and acceptance signal are explici...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening False Positive Reduction Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: container hardening for false-positive reduction. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Validate a suspected issue with the least intrusive authorized evidence and distinguish confirmed from unverified findings. Success means material claims are linked to current primary sources with dates and limitations. ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the prepared result is reproducible, reviewable, a...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means interfaces, dependencies, constraints, and review points are testable bef...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the failure is bounded by observations, on...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means options are compared on user-approved criteria with unc...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means requirements have priorities, evidence, owners, and ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means material claims are linked to current primary sources with dates and limitations. Use pe...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Log Coverage Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for log coverage. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means the prepared result is reproducible, reviewable, and within the ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Log Coverage Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for log coverage. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means interfaces, dependencies, constraints, and review points are testable before build. Use...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Log Coverage Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for log coverage. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means the failure is bounded by observations, one testable hyp...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Log Coverage Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for log coverage. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means options are compared on user-approved criteria with uncertainty and t...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Log Coverage Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for log coverage. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Map expected security events to available telemetry and identify blind spots without disabling or evading controls. Success means requirements have priorities, evidence, owners, and measurable acc...Votes: 0GitHub stars: 2