All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Azure Storage File Datalake Py Failure Triage RecordUse when a reproducible Azure Data Lake Storage SDK for Python symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Data Lake Storage SDK for Python 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 filesystem and path identity, directory operations,...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Input Output ContractUse when the accepted inputs or produced outputs for Azure Data Lake Storage SDK for Python need a checkable boundary. Produce an input/output contract for Azure Data Lake Storage SDK for Python 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 filesystem and path identity, directory ope...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Integration Parity TraceUse when Azure Data Lake Storage SDK for Python exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Data Lake Storage SDK for Python 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 filesystem and path identity, directory operations, ACL scop...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Performance EnvelopeUse when Azure Data Lake Storage SDK for Python must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Data Lake Storage SDK for Python 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 filesystem and path identity, dir...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Permission Boundary ReviewUse when Azure Data Lake Storage SDK for Python may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Data Lake Storage SDK for Python 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 filesystem and path id...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Release Handoff RecordUse when a Azure Data Lake Storage SDK for Python review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Data Lake Storage SDK for Python 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 filesystem and ...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Reproducibility Fixture PlanUse when a Azure Data Lake Storage SDK for Python result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Data Lake Storage SDK for Python 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 i...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Version CompatibilityUse when a Azure Data Lake Storage SDK for Python integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Data Lake Storage SDK for Python 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 filesystem...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Capability Surface MapUse when the actual capability boundary of Azure File Share SDK for TypeScript needs to be distinguished from assumptions. Produce a capability map for Azure File Share SDK for TypeScript 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 share and directory i...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Change Impact AssessmentUse when a proposed Azure File Share SDK for TypeScript version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure File Share SDK for TypeScript 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 share and directory...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Failure Triage RecordUse when a reproducible Azure File Share SDK for TypeScript symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure File Share SDK for TypeScript 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 share and directory identity, access boundary, file opera...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Input Output ContractUse when the accepted inputs or produced outputs for Azure File Share SDK for TypeScript need a checkable boundary. Produce an input/output contract for Azure File Share SDK for TypeScript 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 share and directory identity, access boundary, fi...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Integration Parity TraceUse when Azure File Share SDK for TypeScript exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure File Share SDK for TypeScript 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 share and directory identity, access boundary, file operations, tr...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Performance EnvelopeUse when Azure File Share SDK for TypeScript must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure File Share SDK for TypeScript 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 share and directory identity, access bo...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Permission Boundary ReviewUse when Azure File Share SDK for TypeScript may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure File Share SDK for TypeScript 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 share and directory identity...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Release Handoff RecordUse when a Azure File Share SDK for TypeScript review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure File Share SDK for TypeScript 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 share and directory i...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Reproducibility Fixture PlanUse when a Azure File Share SDK for TypeScript result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure File Share SDK for TypeScript 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 boun...Votes: 0GitHub stars: 2
- Azure Storage File Share Ts Version CompatibilityUse when a Azure File Share SDK for TypeScript integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure File Share SDK for TypeScript 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 share and direct...Votes: 0GitHub stars: 2
- Satellite Cloud Mask ReviewUse when a task involves reviewing cloud and shadow masking choices in satellite imagery before computing surface or land-change indicators 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 ...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Capability Surface MapUse when the actual capability boundary of Vercel token-based CLI needs to be distinguished from assumptions. Produce a capability map for Vercel token-based CLI 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 token origin, project binding, environment sepa...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Change Impact AssessmentUse when a proposed Vercel token-based CLI version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Vercel token-based CLI 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 token origin, project binding, environment se...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Failure Triage RecordUse when a reproducible Vercel token-based CLI symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Vercel token-based CLI 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 token origin, project binding, environment separation, and non-disclosure controls....Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Input Output ContractUse when the accepted inputs or produced outputs for Vercel token-based CLI need a checkable boundary. Produce an input/output contract for Vercel token-based CLI 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 token origin, project binding, environment separation, and non-disclosure c...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Integration Parity TraceUse when Vercel token-based CLI exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Vercel token-based CLI 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 token origin, project binding, environment separation, and non-disclosure controls. Use only...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Performance EnvelopeUse when Vercel token-based CLI must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Vercel token-based CLI 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 token origin, project binding, environment separation, and non-di...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Permission Boundary ReviewUse when Vercel token-based CLI may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Vercel token-based CLI 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 token origin, project binding, environment separation,...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Release Handoff RecordUse when a Vercel token-based CLI review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Vercel token-based CLI 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 token origin, project binding, environment sepa...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Reproducibility Fixture PlanUse when a Vercel token-based CLI result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Vercel token-based CLI 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 token origin, proje...Votes: 0GitHub stars: 2
- Vercel Cli With Tokens Version CompatibilityUse when a Vercel token-based CLI integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Vercel token-based CLI 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 token origin, project binding, environment...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Capability Surface MapUse when the actual capability boundary of AWS ECS and Fargate needs to be distinguished from assumptions. Produce a capability map for AWS ECS and Fargate 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 task definition identity, image digest, deployment he...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Change Impact AssessmentUse when a proposed AWS ECS and Fargate version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for AWS ECS and Fargate 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 task definition identity, image digest, deployment ...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Failure Triage RecordUse when a reproducible AWS ECS and Fargate symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for AWS ECS and Fargate 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 task definition identity, image digest, deployment health, capacity, and service networki...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Input Output ContractUse when the accepted inputs or produced outputs for AWS ECS and Fargate need a checkable boundary. Produce an input/output contract for AWS ECS and Fargate 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 task definition identity, image digest, deployment health, capacity, and service ...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Integration Parity TraceUse when AWS ECS and Fargate exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for AWS ECS and Fargate 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 task definition identity, image digest, deployment health, capacity, and service networking. Use o...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Performance EnvelopeUse when AWS ECS and Fargate must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for AWS ECS and Fargate 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 task definition identity, image digest, deployment health, capacity, an...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Permission Boundary ReviewUse when AWS ECS and Fargate may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for AWS ECS and Fargate 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 task definition identity, image digest, deployment health, c...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Release Handoff RecordUse when a AWS ECS and Fargate review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for AWS ECS and Fargate 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 task definition identity, image digest, deployment he...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Reproducibility Fixture PlanUse when a AWS ECS and Fargate result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for AWS ECS and Fargate 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 task definition identity,...Votes: 0GitHub stars: 2
- Aws Ecs Fargate Version CompatibilityUse when a AWS ECS and Fargate integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for AWS ECS and Fargate 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 task definition identity, image digest, deployme...Votes: 0GitHub stars: 2
- Azure Aks Capability Surface MapUse when the actual capability boundary of Azure Kubernetes Service needs to be distinguished from assumptions. Produce a capability map for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, wor...Votes: 0GitHub stars: 2
- Azure Aks Change Impact AssessmentUse when a proposed Azure Kubernetes Service version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, w...Votes: 0GitHub stars: 2
- Azure Aks Failure Triage RecordUse when a reproducible Azure Kubernetes Service symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, workload compatibility, networking, and...Votes: 0GitHub stars: 2
- Azure Aks Input Output ContractUse when the accepted inputs or produced outputs for Azure Kubernetes Service need a checkable boundary. Produce an input/output contract for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, workload compatibility, network...Votes: 0GitHub stars: 2
- Azure Aks Integration Parity TraceUse when Azure Kubernetes Service exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, workload compatibility, networking, and recovery...Votes: 0GitHub stars: 2
- Azure Aks Performance EnvelopeUse when Azure Kubernetes Service must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, workload compatibilit...Votes: 0GitHub stars: 2
- Azure Aks Permission Boundary ReviewUse when Azure Kubernetes Service may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, workload c...Votes: 0GitHub stars: 2
- Azure Aks Release Handoff RecordUse when a Azure Kubernetes Service review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Kubernetes Service 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 cluster identity, node-pool boundaries, wor...Votes: 0GitHub stars: 2
- Azure Aks Reproducibility Fixture PlanUse when a Azure Kubernetes Service result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Kubernetes Service 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 cluster identit...Votes: 0GitHub stars: 2
- Azure Aks Version CompatibilityUse when a Azure Kubernetes Service integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Kubernetes Service 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 cluster identity, node-pool boundaries...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Approval Evidence PacketUse when a container attestation subject binding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the attestation verification worksheet 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; the statement verifies against the exact artifact and expected policy, without treating signature presence al...Votes: 0GitHub stars: 2