All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Growth Evidence Referral Source Completeness ReconciliationUse when the referral and partner-source quality workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the referral-source reconciliation 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Exception Triage QueueUse when the referral and partner-source quality workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the referral-source reconciliation 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Recovery Readiness DrillUse when the referral and partner-source quality workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the referral-source reconciliation 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Scenario Sensitivity MatrixUse when the referral and partner-source quality team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the referral-source reconciliation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Scope Intake GateUse when a new referral and partner-source quality request needs a bounded work scope to produce a scoped intake card for the referral-source reconciliation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; source assignments reconcile to the taxonomy and missing values remain visible. 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
- Growth Evidence Referral Source Source Provenance LedgerUse when a decision about referral and partner-source quality depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the referral-source reconciliation. Success means each material claim has a source, version/date, location, and confidence note; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Growth Evidence Referral Source Threshold Rule CheckUse when a referral and partner-source quality decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the referral-source reconciliation 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; source assignments reconcile to the taxonomy and missing values remain visible. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Approval Evidence PacketUse when a search-content decay diagnosis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Change Impact TraceUse when a version, rule, source, or stakeholder change may affect search-content decay diagnosis to produce a before/after change record and impact map for the content-decay evidence brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Closeout Handoff LedgerUse when a search-content decay diagnosis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Completeness ReconciliationUse when the search-content decay diagnosis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Exception Triage QueueUse when the search-content decay diagnosis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Recovery Readiness DrillUse when the search-content decay diagnosis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Scenario Sensitivity MatrixUse when the search-content decay diagnosis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the content-decay evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Scope Intake GateUse when a new search-content decay diagnosis request needs a bounded work scope to produce a scoped intake card for the content-decay evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Source Provenance LedgerUse when a decision about search-content decay diagnosis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the content-decay evidence brief. Success means each material claim has a source, version/date, location, and confidence note; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Growth Evidence Seo Decay Threshold Rule CheckUse when a search-content decay diagnosis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the content-decay evidence brief 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; declines are compared across equivalent windows and causes are presented as hypotheses. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Capability Surface MapUse when the actual capability boundary of Meeting record distillation needs to be distinguished from assumptions. Produce a capability map for Meeting record distillation 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 transcript provenance, speaker uncert...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Change Impact AssessmentUse when a proposed Meeting record distillation version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Meeting record distillation 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 transcript provenance, speaker unce...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Failure Triage RecordUse when a reproducible Meeting record distillation symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Meeting record distillation 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 transcript provenance, speaker uncertainty, decision/action separation, a...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Input Output ContractUse when the accepted inputs or produced outputs for Meeting record distillation need a checkable boundary. Produce an input/output contract for Meeting record distillation 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 transcript provenance, speaker uncertainty, decision/action separ...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Integration Parity TraceUse when Meeting record distillation exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Meeting record distillation 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 transcript provenance, speaker uncertainty, decision/action separation, and privac...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Performance EnvelopeUse when Meeting record distillation must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Meeting record distillation 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 transcript provenance, speaker uncertainty, decision/ac...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Permission Boundary ReviewUse when Meeting record distillation may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Meeting record distillation 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 transcript provenance, speaker uncertainty, ...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Release Handoff RecordUse when a Meeting record distillation review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Meeting record distillation 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 transcript provenance, speaker uncert...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Reproducibility Fixture PlanUse when a Meeting record distillation result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Meeting record distillation 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 transcrip...Votes: 0GitHub stars: 2
- Meeting Distiller Pro Version CompatibilityUse when a Meeting record distillation integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Meeting record distillation 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 transcript provenance, speaker u...Votes: 0GitHub stars: 2
- Obsidian Bases Capability Surface MapUse when the actual capability boundary of Obsidian Bases needs to be distinguished from assumptions. Produce a capability map for Obsidian Bases 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 property definitions, views, filters, formulas, source files, a...Votes: 0GitHub stars: 2
- Obsidian Bases Change Impact AssessmentUse when a proposed Obsidian Bases version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Obsidian Bases 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 property definitions, views, filters, formulas, source files,...Votes: 0GitHub stars: 2
- Obsidian Bases Failure Triage RecordUse when a reproducible Obsidian Bases symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Obsidian Bases 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 property definitions, views, filters, formulas, source files, and displayed-result parity. Use only...Votes: 0GitHub stars: 2
- Obsidian Bases Input Output ContractUse when the accepted inputs or produced outputs for Obsidian Bases need a checkable boundary. Produce an input/output contract for Obsidian Bases 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 property definitions, views, filters, formulas, source files, and displayed-result parity. ...Votes: 0GitHub stars: 2
- Obsidian Bases Integration Parity TraceUse when Obsidian Bases exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Obsidian Bases 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 property definitions, views, filters, formulas, source files, and displayed-result parity. Use only authoriz...Votes: 0GitHub stars: 2
- Obsidian Bases Performance EnvelopeUse when Obsidian Bases must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Obsidian Bases 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 property definitions, views, filters, formulas, source files, and displayed-resul...Votes: 0GitHub stars: 2
- Obsidian Bases Permission Boundary ReviewUse when Obsidian Bases may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Obsidian Bases 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 property definitions, views, filters, formulas, source files, and disp...Votes: 0GitHub stars: 2
- Obsidian Bases Release Handoff RecordUse when a Obsidian Bases review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Obsidian Bases 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 property definitions, views, filters, formulas, source files, a...Votes: 0GitHub stars: 2
- Obsidian Bases Reproducibility Fixture PlanUse when a Obsidian Bases result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Obsidian Bases 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 property definitions, views, filter...Votes: 0GitHub stars: 2
- Obsidian Bases Version CompatibilityUse when a Obsidian Bases integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Obsidian Bases 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 property definitions, views, filters, formulas, source fil...Votes: 0GitHub stars: 2
- Obsidian Cli Capability Surface MapUse when the actual capability boundary of Obsidian CLI and vault operations needs to be distinguished from assumptions. Produce a capability map for Obsidian CLI and vault 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 vault path identity, file...Votes: 0GitHub stars: 2
- Obsidian Cli Change Impact AssessmentUse when a proposed Obsidian CLI and vault operations version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Obsidian CLI and vault 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 vault path identity, fi...Votes: 0GitHub stars: 2
- Obsidian Cli Failure Triage RecordUse when a reproducible Obsidian CLI and vault operations symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Obsidian CLI and vault 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 vault path identity, file selection, command scope, plugin bo...Votes: 0GitHub stars: 2
- Obsidian Cli Input Output ContractUse when the accepted inputs or produced outputs for Obsidian CLI and vault operations need a checkable boundary. Produce an input/output contract for Obsidian CLI and vault 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 vault path identity, file selection, command scope, p...Votes: 0GitHub stars: 2
- Obsidian Cli Integration Parity TraceUse when Obsidian CLI and vault operations exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Obsidian CLI and vault 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 vault path identity, file selection, command scope, plugin boundary, a...Votes: 0GitHub stars: 2
- Obsidian Cli Performance EnvelopeUse when Obsidian CLI and vault operations must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Obsidian CLI and vault 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 vault path identity, file selection, comman...Votes: 0GitHub stars: 2
- Obsidian Cli Permission Boundary ReviewUse when Obsidian CLI and vault operations may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Obsidian CLI and vault 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 vault path identity, file select...Votes: 0GitHub stars: 2
- Obsidian Cli Release Handoff RecordUse when a Obsidian CLI and vault operations review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Obsidian CLI and vault 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 vault path identity, file...Votes: 0GitHub stars: 2
- Obsidian Cli Reproducibility Fixture PlanUse when a Obsidian CLI and vault operations result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Obsidian CLI and vault 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 ...Votes: 0GitHub stars: 2
- Obsidian Cli Version CompatibilityUse when a Obsidian CLI and vault operations integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Obsidian CLI and vault 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 vault path identity,...Votes: 0GitHub stars: 2
- Obsidian Markdown Capability Surface MapUse when the actual capability boundary of Obsidian Markdown needs to be distinguished from assumptions. Produce a capability map for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file...Votes: 0GitHub stars: 2
- Obsidian Markdown Change Impact AssessmentUse when a proposed Obsidian Markdown version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and fi...Votes: 0GitHub stars: 2
- Obsidian Markdown Failure Triage RecordUse when a reproducible Obsidian Markdown symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Obsidian Markdown 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 frontmatter, wikilink targets, embeds, callouts, and file identity. Use only authorized local...Votes: 0GitHub stars: 2