All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Obsidian Markdown Input Output ContractUse when the accepted inputs or produced outputs for Obsidian Markdown need a checkable boundary. Produce an input/output contract for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file identity. Use only authoriz...Votes: 0GitHub stars: 2
- Obsidian Markdown Integration Parity TraceUse when Obsidian Markdown exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file identity. Use only authorized local evidence...Votes: 0GitHub stars: 2
- Obsidian Markdown Performance EnvelopeUse when Obsidian Markdown must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file identity. Use onl...Votes: 0GitHub stars: 2
- Obsidian Markdown Permission Boundary ReviewUse when Obsidian Markdown may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file identi...Votes: 0GitHub stars: 2
- Obsidian Markdown Release Handoff RecordUse when a Obsidian Markdown review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file...Votes: 0GitHub stars: 2
- Obsidian Markdown Reproducibility Fixture PlanUse when a Obsidian Markdown result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Obsidian Markdown 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 frontmatter, wikilink targets...Votes: 0GitHub stars: 2
- Obsidian Markdown Version CompatibilityUse when a Obsidian Markdown integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and...Votes: 0GitHub stars: 2
- One Drive Automation Capability Surface MapUse when the actual capability boundary of OneDrive file operations needs to be distinguished from assumptions. Produce a capability map for OneDrive file 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 drive and item identity, search scope, uplo...Votes: 0GitHub stars: 2
- One Drive Automation Change Impact AssessmentUse when a proposed OneDrive file operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for OneDrive file 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 drive and item identity, search scope, up...Votes: 0GitHub stars: 2
- One Drive Automation Failure Triage RecordUse when a reproducible OneDrive file operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for OneDrive file 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 drive and item identity, search scope, upload/download boundary, sharing, and v...Votes: 0GitHub stars: 2
- One Drive Automation Input Output ContractUse when the accepted inputs or produced outputs for OneDrive file operations need a checkable boundary. Produce an input/output contract for OneDrive file 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 drive and item identity, search scope, upload/download boundary, sharin...Votes: 0GitHub stars: 2
- One Drive Automation Integration Parity TraceUse when OneDrive file operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for OneDrive file 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 drive and item identity, search scope, upload/download boundary, sharing, and version hi...Votes: 0GitHub stars: 2
- One Drive Automation Performance EnvelopeUse when OneDrive file operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for OneDrive file 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 drive and item identity, search scope, upload/download bounda...Votes: 0GitHub stars: 2
- One Drive Automation Permission Boundary ReviewUse when OneDrive file operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for OneDrive file 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 drive and item identity, search scope, upload/down...Votes: 0GitHub stars: 2
- One Drive Automation Release Handoff RecordUse when a OneDrive file operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for OneDrive file 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 drive and item identity, search scope, uplo...Votes: 0GitHub stars: 2
- One Drive Automation Reproducibility Fixture PlanUse when a OneDrive file operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for OneDrive file 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 drive and item ...Votes: 0GitHub stars: 2
- One Drive Automation Version CompatibilityUse when a OneDrive file operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for OneDrive file 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 drive and item identity, search scope,...Votes: 0GitHub stars: 2
- Portfolio Exposure And Risk Limit AuditUse when a task involves checking portfolio exposures, concentration, leverage, and predefined risk limits 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, financi...Votes: 0GitHub stars: 2
- Product Ops Discovery Approval Evidence PacketUse when a product discovery result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the discovery evidence set 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; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Product Ops Discovery Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product discovery to produce a before/after change record and impact map for the discovery evidence set. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Product Ops Discovery Closeout Handoff LedgerUse when a product discovery work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the discovery evidence set with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Product Ops Discovery Completeness ReconciliationUse when the product discovery workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the discovery evidence set 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; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Product Ops Discovery Exception Triage QueueUse when the product discovery workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the discovery evidence set 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; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Product Ops Discovery Recovery Readiness DrillUse when the product discovery workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the discovery evidence set 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; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Product Ops Discovery Scenario Sensitivity MatrixUse when the product discovery team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the discovery evidence set with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and...Votes: 0GitHub stars: 2
- Product Ops Discovery Scope Intake GateUse when a new product discovery request needs a bounded work scope to produce a scoped intake card for the discovery evidence set. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek app...Votes: 0GitHub stars: 2
- Product Ops Discovery Source Provenance LedgerUse when a decision about product discovery depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the discovery evidence set. Success means each material claim has a source, version/date, location, and confidence note; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three ...Votes: 0GitHub stars: 2
- Product Ops Discovery Threshold Rule CheckUse when a product discovery decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the discovery evidence set 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; each insight is traceable to evidence and counterexamples are preserved. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Product Ops Experiments Approval Evidence PacketUse when a product experiments result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the experiment specification 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; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Product Ops Experiments Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product experiments to produce a before/after change record and impact map for the experiment specification. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Product Ops Experiments Closeout Handoff LedgerUse when a product experiments work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the experiment specification with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Product Ops Experiments Completeness ReconciliationUse when the product experiments workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the experiment specification 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; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Product Ops Experiments Exception Triage QueueUse when the product experiments workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the experiment specification 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; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Product Ops Experiments Recovery Readiness DrillUse when the product experiments workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the experiment specification 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; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Product Ops Experiments Scenario Sensitivity MatrixUse when the product experiments team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the experiment specification with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Product Ops Experiments Scope Intake GateUse when a new product experiments request needs a bounded work scope to produce a scoped intake card for the experiment specification. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and see...Votes: 0GitHub stars: 2
- Product Ops Experiments Source Provenance LedgerUse when a decision about product experiments depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the experiment specification. Success means each material claim has a source, version/date, location, and confidence note; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to t...Votes: 0GitHub stars: 2
- Product Ops Experiments Threshold Rule CheckUse when a product experiments decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the experiment specification 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; primary metric, guardrails, and stopping rules are fixed before exposure. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Product Ops Feedback Approval Evidence PacketUse when a customer feedback operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the feedback-to-decision ledger 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; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Product Ops Feedback Change Impact TraceUse when a version, rule, source, or stakeholder change may affect customer feedback operations to produce a before/after change record and impact map for the feedback-to-decision ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Product Ops Feedback Closeout Handoff LedgerUse when a customer feedback operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the feedback-to-decision ledger with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Product Ops Feedback Completeness ReconciliationUse when the customer feedback operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the feedback-to-decision ledger 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; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Product Ops Feedback Exception Triage QueueUse when the customer feedback operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the feedback-to-decision ledger 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; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Product Ops Feedback Recovery Readiness DrillUse when the customer feedback operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the feedback-to-decision ledger 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; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Product Ops Feedback Scenario Sensitivity MatrixUse when the customer feedback operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the feedback-to-decision ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Product Ops Feedback Scope Intake GateUse when a new customer feedback operations request needs a bounded work scope to produce a scoped intake card for the feedback-to-decision ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passe...Votes: 0GitHub stars: 2
- Product Ops Feedback Source Provenance LedgerUse when a decision about customer feedback operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the feedback-to-decision ledger. Success means each material claim has a source, version/date, location, and confidence note; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Product Ops Feedback Threshold Rule CheckUse when a customer feedback operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the feedback-to-decision ledger 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; every theme has sample context, confidence, and a recorded disposition. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Product Ops Platform Approval Evidence PacketUse when a product platform and API operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the compatibility decision record 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; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Product Ops Platform Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product platform and API operations to produce a before/after change record and impact map for the compatibility decision record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all known consumers have a compatible path or an explicitly approved migration. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2