All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Copilot Sdk Custom Agent Tool Scope AuditUse when a task involves auditing tool access assigned to custom agents within an SDK session to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change producti...Votes: 0GitHub stars: 2
- Copilot Sdk Event Subscription Cleanup ReviewUse when a task involves reviewing subscription registration and removal in a long-lived SDK host to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change prod...Votes: 0GitHub stars: 2
- Copilot Sdk Feature Compatibility MatrixUse when a task involves mapping required SDK features against current language bindings and CLI versions to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or cha...Votes: 0GitHub stars: 2
- Copilot Sdk Final Answer Completion DetectionUse when a task involves determining when an SDK session has completed a user-facing answer rather than intermediate tool activity to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, sen...Votes: 0GitHub stars: 2
- Copilot Sdk Hook Retry Budget ReviewUse when a task involves setting bounded retry and abort behavior for SDK error and stop hooks to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change product...Votes: 0GitHub stars: 2
- Copilot Sdk Mcp Connection Lifecycle ReviewUse when a task involves reviewing how an SDK session starts, scopes, monitors, and shuts down MCP connections to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, o...Votes: 0GitHub stars: 2
- Copilot Sdk Permission Handler Fail Closed ReviewUse when a task involves reviewing default behavior when an SDK permission callback errors, times out, or returns malformed data to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send ...Votes: 0GitHub stars: 2
- Copilot Sdk Post Tool Result Provenance ReviewUse when a task involves checking that post-tool hooks preserve the identity and trust level of tool output to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or c...Votes: 0GitHub stars: 2
- Copilot Sdk Pre Tool Argument ValidationUse when a task involves validating tool arguments intercepted or modified before SDK tool execution to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change p...Votes: 0GitHub stars: 2
- Copilot Sdk Remote Session Link Sharing ReviewUse when a task involves reviewing controls around links that expose a local SDK session through a remote interface to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writ...Votes: 0GitHub stars: 2
- Copilot Sdk Remote Session Permission BoundaryUse when a task involves checking whether remote participants can expand the local SDK session's tool authority to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, ...Votes: 0GitHub stars: 2
- Copilot Sdk Resume Permission RevalidationUse when a task involves checking that tool permissions are recalculated when a persisted session resumes to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or cha...Votes: 0GitHub stars: 2
- Copilot Sdk Session Event Ordering AuditUse when a task involves checking event ordering and correlation in asynchronous Copilot SDK consumers to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change...Votes: 0GitHub stars: 2
- Copilot Sdk Session Id Privacy ReviewUse when a task involves reviewing identifiers used to create and resume persistent Copilot SDK sessions to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or chan...Votes: 0GitHub stars: 2
- Copilot Sdk Session Lifecycle CleanupUse when a task involves reviewing client and session startup, completion, cancellation, and cleanup in a Copilot SDK integration to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send...Votes: 0GitHub stars: 2
- Copilot Sdk Session Owner Authorization ReviewUse when a task involves checking that only the owning principal can inspect, resume, or control a persisted Copilot session to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send exte...Votes: 0GitHub stars: 2
- Copilot Sdk Session Persistence ConfidentialityUse when a task involves checking confidentiality controls for conversation and tool state persisted by an SDK to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, o...Votes: 0GitHub stars: 2
- Copilot Sdk Session Retention And Deletion AuditUse when a task involves auditing persistence, retention, export, and deletion of Copilot SDK session state to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or c...Votes: 0GitHub stars: 2
- Copilot Sdk Session Working Directory ScopeUse when a task involves auditing filesystem boundaries configured for a persistent or resumed SDK session to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or ch...Votes: 0GitHub stars: 2
- Copilot Sdk Stale Session Recovery TestUse when a task involves testing recovery when a persisted SDK session is incomplete, expired, or inconsistent to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, o...Votes: 0GitHub stars: 2
- Copilot Sdk Stream Cancellation CleanupUse when a task involves checking that cancelling a streaming response stops downstream work and releases resources to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writ...Votes: 0GitHub stars: 2
- Copilot Sdk Streaming Delta Assembly ValidationUse when a task involves validating how partial streamed messages are assembled into a final response to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change ...Votes: 0GitHub stars: 2
- Copilot Sdk Structured Output Schema ValidationUse when a task involves validating structured SDK responses against a consumer's required schema to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change prod...Votes: 0GitHub stars: 2
- Copilot Sdk Subagent Concurrency BudgetUse when a task involves planning bounded parallel subagent work in an SDK application to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change production poli...Votes: 0GitHub stars: 2
- Copilot Sdk Tool Failure Hook ClassificationUse when a task involves checking that failed tool calls reach the correct SDK failure-handling path to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or change p...Votes: 0GitHub stars: 2
- Copilot Sdk Tool Result Size BudgetUse when a task involves controlling size and sensitivity of tool results passed back into an SDK session to record the product, runtime and repository version, identity, trust boundary, data sensitivity, controlling artifact, owner, and approval scope before applying the method. Distinguish documented behavior from tested behavior, verify with a bounded reproducible case, preserve provenance, and report compatibility and uncertainty. Do not install, grant access, send external writes, or cha...Votes: 0GitHub stars: 2
- Create LlmsUse when a task involves creating or updating an llms.txt-style documentation index that helps readers and tools navigate an existing project to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain;...Votes: 0GitHub stars: 2
- Documentation Automation Linkcheck GateUse when an automation edits docs from source changes or repository events to create or update a documentation diff and link-check report. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: all changed claims match source evidence and changed links resolve in the intended site. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Elevenlabs Conversational Agent DesignUse when a task involves designing or configuring a conversational voice agent using ElevenLabs' current agent products to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run...Votes: 0GitHub stars: 2
- Fal Platform Capability Surface MapUse when the actual capability boundary of FAL platform operations needs to be distinguished from assumptions. Produce a capability map for FAL platform operations 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 model or endpoint identity, request state, us...Votes: 0GitHub stars: 2
- Fal Platform Change Impact AssessmentUse when a proposed FAL platform operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for FAL platform operations 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 model or endpoint identity, request state, ...Votes: 0GitHub stars: 2
- Fal Platform Failure Triage RecordUse when a reproducible FAL platform operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for FAL platform operations 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 model or endpoint identity, request state, usage limits, and returned asset prove...Votes: 0GitHub stars: 2
- Fal Platform Input Output ContractUse when the accepted inputs or produced outputs for FAL platform operations need a checkable boundary. Produce an input/output contract for FAL platform operations 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 model or endpoint identity, request state, usage limits, and returned ass...Votes: 0GitHub stars: 2
- Fal Platform Integration Parity TraceUse when FAL platform operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for FAL platform operations 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 model or endpoint identity, request state, usage limits, and returned asset provenance. Us...Votes: 0GitHub stars: 2
- Fal Platform Performance EnvelopeUse when FAL platform operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for FAL platform operations 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 model or endpoint identity, request state, usage limits, and re...Votes: 0GitHub stars: 2
- Fal Platform Permission Boundary ReviewUse when FAL platform operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for FAL platform operations 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 model or endpoint identity, request state, usage lim...Votes: 0GitHub stars: 2
- Fal Platform Release Handoff RecordUse when a FAL platform operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for FAL platform operations 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 model or endpoint identity, request state, us...Votes: 0GitHub stars: 2
- Fal Platform Reproducibility Fixture PlanUse when a FAL platform operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for FAL platform operations 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 model or endpoint...Votes: 0GitHub stars: 2
- Fal Platform Version CompatibilityUse when a FAL platform operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for FAL platform operations 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 model or endpoint identity, request stat...Votes: 0GitHub stars: 2
- Fal Workflow Capability Surface MapUse when the actual capability boundary of FAL workflow composition needs to be distinguished from assumptions. Produce a capability map for FAL workflow composition 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 workflow inputs, intermediate outputs, asyn...Votes: 0GitHub stars: 2
- Fal Workflow Change Impact AssessmentUse when a proposed FAL workflow composition version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for FAL workflow composition 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 workflow inputs, intermediate outputs, as...Votes: 0GitHub stars: 2
- Fal Workflow Failure Triage RecordUse when a reproducible FAL workflow composition symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for FAL workflow composition 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 workflow inputs, intermediate outputs, asynchronous state, and failure boundari...Votes: 0GitHub stars: 2
- Fal Workflow Input Output ContractUse when the accepted inputs or produced outputs for FAL workflow composition need a checkable boundary. Produce an input/output contract for FAL workflow composition 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 workflow inputs, intermediate outputs, asynchronous state, and failure ...Votes: 0GitHub stars: 2
- Fal Workflow Integration Parity TraceUse when FAL workflow composition exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for FAL workflow composition 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 workflow inputs, intermediate outputs, asynchronous state, and failure boundaries. Use o...Votes: 0GitHub stars: 2
- Fal Workflow Performance EnvelopeUse when FAL workflow composition must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for FAL workflow composition 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 workflow inputs, intermediate outputs, asynchronous state, an...Votes: 0GitHub stars: 2
- Fal Workflow Permission Boundary ReviewUse when FAL workflow composition may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for FAL workflow composition 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 workflow inputs, intermediate outputs, asynchronou...Votes: 0GitHub stars: 2
- Fal Workflow Release Handoff RecordUse when a FAL workflow composition review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for FAL workflow composition 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 workflow inputs, intermediate outputs, asyn...Votes: 0GitHub stars: 2
- Fal Workflow Reproducibility Fixture PlanUse when a FAL workflow composition result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for FAL workflow composition 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 workflow inputs...Votes: 0GitHub stars: 2
- Fal Workflow Version CompatibilityUse when a FAL workflow composition integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for FAL workflow composition 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 workflow inputs, intermediate outputs,...Votes: 0GitHub stars: 2
- Gemini Api Dev Capability Surface MapUse when the actual capability boundary of Gemini API integration needs to be distinguished from assumptions. Produce a capability map for Gemini API integration 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 and model versions, request shape, multi...Votes: 0GitHub stars: 2