All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Azure Search Documents Ts Failure Triage RecordUse when a reproducible Azure AI Search SDK for TypeScript symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure AI Search 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 index schema, query shape, pagination, client version, and ...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Input Output ContractUse when the accepted inputs or produced outputs for Azure AI Search SDK for TypeScript need a checkable boundary. Produce an input/output contract for Azure AI Search 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 index schema, query shape, pagination, client versi...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Integration Parity TraceUse when Azure AI Search SDK for TypeScript exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure AI Search 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 index schema, query shape, pagination, client version, and test-corp...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Performance EnvelopeUse when Azure AI Search 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 AI Search 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 index schema, query shape, pagination, cl...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Permission Boundary ReviewUse when Azure AI Search SDK for TypeScript may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure AI Search 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 index schema, query shape, pag...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Release Handoff RecordUse when a Azure AI Search SDK for TypeScript review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure AI Search 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 index schema, query sha...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Reproducibility Fixture PlanUse when a Azure AI Search SDK for TypeScript result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure AI Search 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 bounde...Votes: 0GitHub stars: 2
- Azure Search Documents Ts Version CompatibilityUse when a Azure AI Search SDK for TypeScript integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure AI Search 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 index schema, quer...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Capability Surface MapUse when the actual capability boundary of Azure Service Bus SDK for Rust needs to be distinguished from assumptions. Produce a capability map for Azure Service Bus SDK for Rust 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 client lifetime, message settle...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Change Impact AssessmentUse when a proposed Azure Service Bus SDK for Rust version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Service Bus SDK for Rust 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 client lifetime, message sett...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Failure Triage RecordUse when a reproducible Azure Service Bus SDK for Rust symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Service Bus SDK for Rust 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 client lifetime, message settlement, session assumptions, retry bou...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Input Output ContractUse when the accepted inputs or produced outputs for Azure Service Bus SDK for Rust need a checkable boundary. Produce an input/output contract for Azure Service Bus SDK for Rust 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 client lifetime, message settlement, session assumptions, r...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Integration Parity TraceUse when Azure Service Bus SDK for Rust exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Service Bus SDK for Rust 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 client lifetime, message settlement, session assumptions, retry boundaries, ...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Performance EnvelopeUse when Azure Service Bus SDK for Rust must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Service Bus SDK for Rust 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 client lifetime, message settlement, session assu...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Permission Boundary ReviewUse when Azure Service Bus SDK for Rust may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Service Bus SDK for Rust 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 client lifetime, message settlement, s...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Release Handoff RecordUse when a Azure Service Bus SDK for Rust review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Service Bus SDK for Rust 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 client lifetime, message settle...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Reproducibility Fixture PlanUse when a Azure Service Bus SDK for Rust result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Service Bus SDK for Rust 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 cli...Votes: 0GitHub stars: 2
- Azure Servicebus Rust Version CompatibilityUse when a Azure Service Bus SDK for Rust integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Service Bus SDK for Rust 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 client lifetime, message s...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Capability Surface MapUse when the actual capability boundary of Azure Service Bus SDK for TypeScript needs to be distinguished from assumptions. Produce a capability map for Azure Service Bus 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 queue/topic identit...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Change Impact AssessmentUse when a proposed Azure Service Bus SDK for TypeScript version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Service Bus 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 queue/topic ident...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Failure Triage RecordUse when a reproducible Azure Service Bus SDK for TypeScript symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Service Bus 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 queue/topic identity, acknowledgement behavior, duplica...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Input Output ContractUse when the accepted inputs or produced outputs for Azure Service Bus SDK for TypeScript need a checkable boundary. Produce an input/output contract for Azure Service Bus 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 queue/topic identity, acknowledgement behavior,...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Integration Parity TraceUse when Azure Service Bus SDK for TypeScript exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Service Bus 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 queue/topic identity, acknowledgement behavior, duplicate handli...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Performance EnvelopeUse when Azure Service Bus 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 Service Bus 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 queue/topic identity, acknowledgement...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Permission Boundary ReviewUse when Azure Service Bus SDK for TypeScript may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Service Bus 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 queue/topic identity, ackn...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Release Handoff RecordUse when a Azure Service Bus SDK for TypeScript review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Service Bus 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 queue/topic identit...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Reproducibility Fixture PlanUse when a Azure Service Bus SDK for TypeScript result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Service Bus 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 bo...Votes: 0GitHub stars: 2
- Azure Servicebus Ts Version CompatibilityUse when a Azure Service Bus SDK for TypeScript integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Service Bus 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 queue/topic id...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Capability Surface MapUse when the actual capability boundary of Azure Speech-to-Text REST for Python needs to be distinguished from assumptions. Produce a capability map for Azure Speech-to-Text REST for Python 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 audio length, reque...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Change Impact AssessmentUse when a proposed Azure Speech-to-Text REST for Python version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Speech-to-Text REST for Python 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 audio length, req...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Failure Triage RecordUse when a reproducible Azure Speech-to-Text REST for Python symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Speech-to-Text REST 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 audio length, request encoding, response confidence, da...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Input Output ContractUse when the accepted inputs or produced outputs for Azure Speech-to-Text REST for Python need a checkable boundary. Produce an input/output contract for Azure Speech-to-Text REST 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 audio length, request encoding, response confid...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Integration Parity TraceUse when Azure Speech-to-Text REST for Python exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Speech-to-Text REST 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 audio length, request encoding, response confidence, data handli...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Performance EnvelopeUse when Azure Speech-to-Text REST 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 Speech-to-Text REST 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 audio length, request encoding, respo...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Permission Boundary ReviewUse when Azure Speech-to-Text REST for Python may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Speech-to-Text REST 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 audio length, request enco...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Release Handoff RecordUse when a Azure Speech-to-Text REST for Python review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Speech-to-Text REST 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 audio length, reque...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Reproducibility Fixture PlanUse when a Azure Speech-to-Text REST for Python result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Speech-to-Text REST 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 is bo...Votes: 0GitHub stars: 2
- Azure Speech To Text Rest Py Version CompatibilityUse when a Azure Speech-to-Text REST for Python integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Speech-to-Text REST 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 audio length, ...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Capability Surface MapUse when the actual capability boundary of Azure Blob Storage SDK for Java needs to be distinguished from assumptions. Produce a capability map for Azure Blob Storage SDK for Java 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 container and object identity...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Change Impact AssessmentUse when a proposed Azure Blob Storage SDK for Java version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Blob Storage SDK for Java 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 container and object identi...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Failure Triage RecordUse when a reproducible Azure Blob Storage SDK for Java symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Blob Storage SDK for Java 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 container and object identity, transfer integrity, metadata, and ...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Input Output ContractUse when the accepted inputs or produced outputs for Azure Blob Storage SDK for Java need a checkable boundary. Produce an input/output contract for Azure Blob Storage SDK for Java 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 container and object identity, transfer integrity, metada...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Integration Parity TraceUse when Azure Blob Storage SDK for Java exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Blob Storage SDK for Java 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 container and object identity, transfer integrity, metadata, and access bo...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Performance EnvelopeUse when Azure Blob Storage SDK for Java must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Blob Storage SDK for Java 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 container and object identity, transfer integri...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Permission Boundary ReviewUse when Azure Blob Storage SDK for Java may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Blob Storage SDK for Java 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 container and object identity, trans...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Release Handoff RecordUse when a Azure Blob Storage SDK for Java review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Blob Storage SDK for Java 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 container and object identity...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Reproducibility Fixture PlanUse when a Azure Blob Storage SDK for Java result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Blob Storage SDK for Java 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 c...Votes: 0GitHub stars: 2
- Azure Storage Blob Java Version CompatibilityUse when a Azure Blob Storage SDK for Java integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Blob Storage SDK for Java 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 container and object ide...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Capability Surface MapUse when the actual capability boundary of Azure Data Lake Storage SDK for Python needs to be distinguished from assumptions. Produce a capability map for Azure Data Lake Storage SDK for Python 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 filesystem and ...Votes: 0GitHub stars: 2
- Azure Storage File Datalake Py Change Impact AssessmentUse when a proposed Azure Data Lake Storage SDK for Python version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Data Lake Storage SDK for Python 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 filesystem an...Votes: 0GitHub stars: 2