All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Data Vector Index Identity Completeness ReconciliationUse when the vector index rebuild identity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the vector index build manifest 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; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Exception Triage QueueUse when the vector index rebuild identity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the vector index build manifest 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; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Recovery Readiness DrillUse when the vector index rebuild identity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the vector index build manifest 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; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Scenario Sensitivity MatrixUse when the vector index rebuild identity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the vector index build manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Scope Intake GateUse when a new vector index rebuild identity request needs a bounded work scope to produce a scoped intake card for the vector index build manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Source Provenance LedgerUse when a decision about vector index rebuild identity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the vector index build manifest. Success means each material claim has a source, version/date, location, and confidence note; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Aas Data Vector Index Identity Threshold Rule CheckUse when a vector index rebuild identity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the vector index build manifest 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; the rebuilt index is attributable and retrieval differences can be tied to a changed input. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Claimable Postgres Capability Surface MapUse when the actual capability boundary of Temporary Postgres database workflows needs to be distinguished from assumptions. Produce a capability map for Temporary Postgres database workflows 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 sandbox identity,...Votes: 0GitHub stars: 2
- Claimable Postgres Change Impact AssessmentUse when a proposed Temporary Postgres database workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Temporary Postgres database workflows 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 sandbox identit...Votes: 0GitHub stars: 2
- Claimable Postgres Failure Triage RecordUse when a reproducible Temporary Postgres database workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Temporary Postgres database workflows 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 sandbox identity, credential scope, network boundary,...Votes: 0GitHub stars: 2
- Claimable Postgres Input Output ContractUse when the accepted inputs or produced outputs for Temporary Postgres database workflows need a checkable boundary. Produce an input/output contract for Temporary Postgres database workflows 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 sandbox identity, credential scope, network b...Votes: 0GitHub stars: 2
- Claimable Postgres Integration Parity TraceUse when Temporary Postgres database workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Temporary Postgres database workflows 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 sandbox identity, credential scope, network boundary, lifecycl...Votes: 0GitHub stars: 2
- Claimable Postgres Performance EnvelopeUse when Temporary Postgres database workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Temporary Postgres database workflows 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 sandbox identity, credential scope,...Votes: 0GitHub stars: 2
- Claimable Postgres Permission Boundary ReviewUse when Temporary Postgres database workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Temporary Postgres database workflows 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 sandbox identity, creden...Votes: 0GitHub stars: 2
- Claimable Postgres Release Handoff RecordUse when a Temporary Postgres database workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Temporary Postgres database workflows 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 sandbox identity,...Votes: 0GitHub stars: 2
- Claimable Postgres Reproducibility Fixture PlanUse when a Temporary Postgres database workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Temporary Postgres database workflows 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 ...Votes: 0GitHub stars: 2
- Claimable Postgres Version CompatibilityUse when a Temporary Postgres database workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Temporary Postgres database workflows 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 sandbox iden...Votes: 0GitHub stars: 2
- Database Engine DevelopmentUse when implementing a database engine, storage layer, query executor, or transaction feature to define the data model and durability guarantees first, then build a small persistent slice with explicit recovery and resource limits. Trigger for page storage, indexing, query planning, transactions, logging, or database compatibility work.Votes: 0GitHub stars: 2
- Database Migration SafetyUse when changing a database schema or transforming persisted data in a live or long-lived application to inspect engine and ORM behavior, plan compatibility across application versions, test against representative data, and define recovery before execution. Trigger for schema migrations, backfills, renames, index changes, or zero-downtime rollout planning.Votes: 0GitHub stars: 2
- Dataverse Python Advanced PatternsUse when a task involves building a Python integration with Microsoft Dataverse using current supported authentication, paging, and API behavior 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 doma...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Capability Surface MapUse when the actual capability boundary of Drizzle ORM integration needs to be distinguished from assumptions. Produce a capability map for Drizzle ORM 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 schema typing, query translation, driver vers...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Change Impact AssessmentUse when a proposed Drizzle ORM integration version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Drizzle ORM integration 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 schema typing, query translation, driver ve...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Failure Triage RecordUse when a reproducible Drizzle ORM integration symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Drizzle ORM integration 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 schema typing, query translation, driver version, transaction scope, and migratio...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Input Output ContractUse when the accepted inputs or produced outputs for Drizzle ORM integration need a checkable boundary. Produce an input/output contract for Drizzle ORM integration 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 schema typing, query translation, driver version, transaction scope, and ...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Integration Parity TraceUse when Drizzle ORM integration exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Drizzle ORM integration 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 schema typing, query translation, driver version, transaction scope, and migration diff. U...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Performance EnvelopeUse when Drizzle ORM integration must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Drizzle ORM integration 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 schema typing, query translation, driver version, transaction s...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Permission Boundary ReviewUse when Drizzle ORM integration may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Drizzle ORM integration 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 schema typing, query translation, driver version, tr...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Release Handoff RecordUse when a Drizzle ORM integration review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Drizzle ORM integration 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 schema typing, query translation, driver vers...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Reproducibility Fixture PlanUse when a Drizzle ORM integration result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Drizzle ORM integration 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 schema typing, qu...Votes: 0GitHub stars: 2
- Drizzle Orm Expert Version CompatibilityUse when a Drizzle ORM integration integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Drizzle ORM integration 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 schema typing, query translation, driver...Votes: 0GitHub stars: 2
- Graph Rag Context Budget EvaluationUse when a task involves measuring whether retrieved graph context improves an answer within a fixed token budget to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, ...Votes: 0GitHub stars: 2
- Knowledge Graph Conflict Detection WorkflowUse when a task involves designing a review queue for incompatible claims in a knowledge graph to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-c...Votes: 0GitHub stars: 2
- Knowledge Graph Data Lineage DesignUse when a task involves designing lineage links from graph assertions to source records and transforms to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial,...Votes: 0GitHub stars: 2
- Knowledge Graph Entity Resolution PlanUse when a task involves planning entity resolution across datasets with conflicting identifiers to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device...Votes: 0GitHub stars: 2
- Knowledge Graph Ingestion Deduplication ReviewUse when a task involves reviewing duplicate detection and idempotency in graph ingestion to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-contro...Votes: 0GitHub stars: 2
- Knowledge Graph Query Quality EvaluationUse when a task involves evaluating graph-query results for completeness, relevance, and provenance to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, dev...Votes: 0GitHub stars: 2
- Knowledge Graph Schema Evolution MigrationUse when a task involves planning a schema change for a knowledge graph with existing consumers to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-...Votes: 0GitHub stars: 2
- Knowledge Graph Temporal Consistency AuditUse when a task involves auditing time-bounded graph facts and relationships for consistency to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-con...Votes: 0GitHub stars: 2
- Neon Postgres Branches Capability Surface MapUse when the actual capability boundary of Neon Postgres branch isolation needs to be distinguished from assumptions. Produce a capability map for Neon Postgres branch isolation 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 branch ancestry, data sensitivi...Votes: 0GitHub stars: 2
- Neon Postgres Branches Change Impact AssessmentUse when a proposed Neon Postgres branch isolation version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Neon Postgres branch isolation 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 branch ancestry, data sensiti...Votes: 0GitHub stars: 2
- Neon Postgres Branches Failure Triage RecordUse when a reproducible Neon Postgres branch isolation symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Neon Postgres branch isolation 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 branch ancestry, data sensitivity, connection identity, reset behav...Votes: 0GitHub stars: 2
- Neon Postgres Branches Input Output ContractUse when the accepted inputs or produced outputs for Neon Postgres branch isolation need a checkable boundary. Produce an input/output contract for Neon Postgres branch isolation 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 branch ancestry, data sensitivity, connection identity, res...Votes: 0GitHub stars: 2
- Neon Postgres Branches Integration Parity TraceUse when Neon Postgres branch isolation exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Neon Postgres branch isolation 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 branch ancestry, data sensitivity, connection identity, reset behavior, and ...Votes: 0GitHub stars: 2
- Neon Postgres Branches Performance EnvelopeUse when Neon Postgres branch isolation must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Neon Postgres branch isolation 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 branch ancestry, data sensitivity, connection ide...Votes: 0GitHub stars: 2
- Neon Postgres Branches Permission Boundary ReviewUse when Neon Postgres branch isolation may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Neon Postgres branch isolation 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 branch ancestry, data sensitivity, con...Votes: 0GitHub stars: 2
- Neon Postgres Branches Release Handoff RecordUse when a Neon Postgres branch isolation review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Neon Postgres branch isolation 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 branch ancestry, data sensitivi...Votes: 0GitHub stars: 2
- Neon Postgres Branches Reproducibility Fixture PlanUse when a Neon Postgres branch isolation result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Neon Postgres branch isolation 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 bra...Votes: 0GitHub stars: 2
- Neon Postgres Branches Version CompatibilityUse when a Neon Postgres branch isolation integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Neon Postgres branch isolation 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 branch ancestry, data sens...Votes: 0GitHub stars: 2
- Nosql Expert Capability Surface MapUse when the actual capability boundary of NoSQL data modeling needs to be distinguished from assumptions. Produce a capability map for NoSQL data modeling 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 access-pattern evidence, key design, consistency assu...Votes: 0GitHub stars: 2
- Nosql Expert Change Impact AssessmentUse when a proposed NoSQL data modeling version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for NoSQL data modeling 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 access-pattern evidence, key design, consistency as...Votes: 0GitHub stars: 2