All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Cloudflare Pages Integration Parity TraceUse when Cloudflare Pages delivery exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Cloudflare Pages delivery showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to build adapter, route behavior, environment bindings, preview identity, and deployment ...Votes: 0GitHub stars: 2
- Cloudflare Pages Performance EnvelopeUse when Cloudflare Pages delivery must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Cloudflare Pages delivery with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to build adapter, route behavior, environment bindings, previe...Votes: 0GitHub stars: 2
- Cloudflare Pages Permission Boundary ReviewUse when Cloudflare Pages delivery may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Cloudflare Pages delivery showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to build adapter, route behavior, environment bindi...Votes: 0GitHub stars: 2
- Cloudflare Pages Release Handoff RecordUse when a Cloudflare Pages delivery review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Cloudflare Pages delivery with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to build adapter, route behavior, environmen...Votes: 0GitHub stars: 2
- Cloudflare Pages Reproducibility Fixture PlanUse when a Cloudflare Pages delivery result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Cloudflare Pages delivery defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to build adapter...Votes: 0GitHub stars: 2
- Cloudflare Pages Version CompatibilityUse when a Cloudflare Pages delivery integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Cloudflare Pages delivery with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to build adapter, route behavior, envir...Votes: 0GitHub stars: 2
- Cloudflare R2 Capability Surface MapUse when the actual capability boundary of Cloudflare R2 object storage needs to be distinguished from assumptions. Produce a capability map for Cloudflare R2 object storage covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to bucket identity, object naming, acc...Votes: 0GitHub stars: 2
- Cloudflare R2 Change Impact AssessmentUse when a proposed Cloudflare R2 object storage version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Cloudflare R2 object storage with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to bucket identity, object naming, a...Votes: 0GitHub stars: 2
- Cloudflare R2 Failure Triage RecordUse when a reproducible Cloudflare R2 object storage symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Cloudflare R2 object storage with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to bucket identity, object naming, access policy, lifecycle, and signed-li...Votes: 0GitHub stars: 2
- Cloudflare R2 Input Output ContractUse when the accepted inputs or produced outputs for Cloudflare R2 object storage need a checkable boundary. Produce an input/output contract for Cloudflare R2 object storage with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to bucket identity, object naming, access policy, lifecycle, and s...Votes: 0GitHub stars: 2
- Cloudflare R2 Integration Parity TraceUse when Cloudflare R2 object storage exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Cloudflare R2 object storage showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to bucket identity, object naming, access policy, lifecycle, and signed-link exposu...Votes: 0GitHub stars: 2
- Cloudflare R2 Performance EnvelopeUse when Cloudflare R2 object storage must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Cloudflare R2 object storage with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to bucket identity, object naming, access policy, lifecy...Votes: 0GitHub stars: 2
- Cloudflare R2 Permission Boundary ReviewUse when Cloudflare R2 object storage may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Cloudflare R2 object storage showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to bucket identity, object naming, access pol...Votes: 0GitHub stars: 2
- Cloudflare R2 Release Handoff RecordUse when a Cloudflare R2 object storage review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Cloudflare R2 object storage with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to bucket identity, object naming, acc...Votes: 0GitHub stars: 2
- Cloudflare R2 Reproducibility Fixture PlanUse when a Cloudflare R2 object storage result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Cloudflare R2 object storage defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to bucket ...Votes: 0GitHub stars: 2
- Cloudflare R2 Version CompatibilityUse when a Cloudflare R2 object storage integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Cloudflare R2 object storage with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to bucket identity, object naming...Votes: 0GitHub stars: 2
- Cloudflare Workers Capability Surface MapUse when the actual capability boundary of Cloudflare Workers runtime needs to be distinguished from assumptions. Produce a capability map for Cloudflare Workers runtime covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to compatibility date, bindings, execution...Votes: 0GitHub stars: 2
- Cloudflare Workers Change Impact AssessmentUse when a proposed Cloudflare Workers runtime version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Cloudflare Workers runtime with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to compatibility date, bindings, executi...Votes: 0GitHub stars: 2
- Cloudflare Workers Failure Triage RecordUse when a reproducible Cloudflare Workers runtime symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Cloudflare Workers runtime with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to compatibility date, bindings, execution limits, stateful dependencies, and ...Votes: 0GitHub stars: 2
- Cloudflare Workers Input Output ContractUse when the accepted inputs or produced outputs for Cloudflare Workers runtime need a checkable boundary. Produce an input/output contract for Cloudflare Workers runtime with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to compatibility date, bindings, execution limits, stateful dependenci...Votes: 0GitHub stars: 2
- Cloudflare Workers Integration Parity TraceUse when Cloudflare Workers runtime exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Cloudflare Workers runtime showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to compatibility date, bindings, execution limits, stateful dependencies, and route exp...Votes: 0GitHub stars: 2
- Cloudflare Workers Performance EnvelopeUse when Cloudflare Workers runtime must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Cloudflare Workers runtime with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to compatibility date, bindings, execution limits, stateful ...Votes: 0GitHub stars: 2
- Cloudflare Workers Permission Boundary ReviewUse when Cloudflare Workers runtime may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Cloudflare Workers runtime showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to compatibility date, bindings, execution limits...Votes: 0GitHub stars: 2
- Cloudflare Workers Release Handoff RecordUse when a Cloudflare Workers runtime review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Cloudflare Workers runtime with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to compatibility date, bindings, execution...Votes: 0GitHub stars: 2
- Cloudflare Workers Reproducibility Fixture PlanUse when a Cloudflare Workers runtime result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Cloudflare Workers runtime defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to compatibili...Votes: 0GitHub stars: 2
- Cloudflare Workers Version CompatibilityUse when a Cloudflare Workers runtime integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Cloudflare Workers runtime with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to compatibility date, bindings, exec...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Capability Surface MapUse when the actual capability boundary of Cloudflare Zero Trust access boundaries needs to be distinguished from assumptions. Produce a capability map for Cloudflare Zero Trust access boundaries covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to application i...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Change Impact AssessmentUse when a proposed Cloudflare Zero Trust access boundaries version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Cloudflare Zero Trust access boundaries with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to application...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Failure Triage RecordUse when a reproducible Cloudflare Zero Trust access boundaries symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Cloudflare Zero Trust access boundaries with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to application identity, policy subjects, device pos...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Input Output ContractUse when the accepted inputs or produced outputs for Cloudflare Zero Trust access boundaries need a checkable boundary. Produce an input/output contract for Cloudflare Zero Trust access boundaries with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to application identity, policy subjects, de...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Integration Parity TraceUse when Cloudflare Zero Trust access boundaries exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Cloudflare Zero Trust access boundaries showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to application identity, policy subjects, device posture evid...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Performance EnvelopeUse when Cloudflare Zero Trust access boundaries must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Cloudflare Zero Trust access boundaries with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to application identity, policy su...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Permission Boundary ReviewUse when Cloudflare Zero Trust access boundaries may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Cloudflare Zero Trust access boundaries showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to application identity...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Release Handoff RecordUse when a Cloudflare Zero Trust access boundaries review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Cloudflare Zero Trust access boundaries with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to application i...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Reproducibility Fixture PlanUse when a Cloudflare Zero Trust access boundaries result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Cloudflare Zero Trust access boundaries defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review...Votes: 0GitHub stars: 2
- Cloudflare Zero Trust Version CompatibilityUse when a Cloudflare Zero Trust access boundaries integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Cloudflare Zero Trust access boundaries with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to applicat...Votes: 0GitHub stars: 2
- Network Science AnalysisUse when a task involves designing a network analysis with explicit node, edge, direction, weight, sampling, and null-model definitions to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external writ...Votes: 0GitHub stars: 2
- Network Stack DevelopmentUse when implementing packet parsing, transport behavior, protocol layering, or a network-stack component to select a bounded protocol subset, define byte-level invariants and state transitions, and validate malformed traffic in an isolated test harness before opening sockets. Trigger for link, network, or transport protocol work.Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Approval Evidence PacketUse when a content security policy report analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the CSP violation triage summary containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Change Impact TraceUse when a version, rule, source, or stakeholder change may affect content security policy report analysis to produce a before/after change record and impact map for the CSP violation triage summary. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Closeout Handoff LedgerUse when a content security policy report analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the CSP violation triage summary with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Completeness ReconciliationUse when the content security policy report analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the CSP violation triage summary with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Exception Triage QueueUse when the content security policy report analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the CSP violation triage summary with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Recovery Readiness DrillUse when the content security policy report analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the CSP violation triage summary with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Scenario Sensitivity MatrixUse when the content security policy report analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the CSP violation triage summary with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Scope Intake GateUse when a new content security policy report analysis request needs a bounded work scope to produce a scoped intake card for the CSP violation triage summary. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Source Provenance LedgerUse when a decision about content security policy report analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the CSP violation triage summary. Success means each material claim has a source, version/date, location, and confidence note; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...Votes: 0GitHub stars: 2
- Aas Secure Delivery Csp Report Threshold Rule CheckUse when a content security policy report analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the CSP violation triage summary showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Approval Evidence PacketUse when a dependency vulnerability reachability triage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the dependency reachability evidence table containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; priority reflects verified exposure rather than severity label alone. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Change Impact TraceUse when a version, rule, source, or stakeholder change may affect dependency vulnerability reachability triage to produce a before/after change record and impact map for the dependency reachability evidence table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2