All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Saas Seat Assignment Approval Evidence PacketUse when a paid seat assignment reconciliation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Change Impact TraceUse when a version, rule, source, or stakeholder change may affect paid seat assignment reconciliation to produce a before/after change record and impact map for the paid-seat inventory. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Closeout Handoff LedgerUse when a paid seat assignment reconciliation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Completeness ReconciliationUse when the paid seat assignment reconciliation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Exception Triage QueueUse when the paid seat assignment reconciliation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Recovery Readiness DrillUse when the paid seat assignment reconciliation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Scenario Sensitivity MatrixUse when the paid seat assignment reconciliation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the paid-seat inventory with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Scope Intake GateUse when a new paid seat assignment reconciliation request needs a bounded work scope to produce a scoped intake card for the paid-seat inventory. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pass...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Source Provenance LedgerUse when a decision about paid seat assignment reconciliation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the paid-seat inventory. Success means each material claim has a source, version/date, location, and confidence note; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Aas Saas Seat Assignment Threshold Rule CheckUse when a paid seat assignment reconciliation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the paid-seat inventory 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; billable and active seats are distinguished without revoking real access. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Approval Evidence PacketUse when a trial conversion cohort denominator result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the trial conversion cohort definition 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; the denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Change Impact TraceUse when a version, rule, source, or stakeholder change may affect trial conversion cohort denominator to produce a before/after change record and impact map for the trial conversion cohort definition. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Closeout Handoff LedgerUse when a trial conversion cohort denominator work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the trial conversion cohort definition 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; the denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Completeness ReconciliationUse when the trial conversion cohort denominator workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the trial conversion cohort definition 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 denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Exception Triage QueueUse when the trial conversion cohort denominator workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the trial conversion cohort definition 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 denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Recovery Readiness DrillUse when the trial conversion cohort denominator workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the trial conversion cohort definition 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 denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Scenario Sensitivity MatrixUse when the trial conversion cohort denominator team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the trial conversion cohort definition with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Scope Intake GateUse when a new trial conversion cohort denominator request needs a bounded work scope to produce a scoped intake card for the trial conversion cohort definition. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the denominator can be reproduced and each exclusion has a stated rule. 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
- Aas Saas Trial Denominator Source Provenance LedgerUse when a decision about trial conversion cohort denominator depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the trial conversion cohort definition. Success means each material claim has a source, version/date, location, and confidence note; the denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Aas Saas Trial Denominator Threshold Rule CheckUse when a trial conversion cohort denominator decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the trial conversion cohort definition 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 denominator can be reproduced and each exclusion has a stated rule. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Asana Automation Capability Surface MapUse when the actual capability boundary of Asana project and task workflows needs to be distinguished from assumptions. Produce a capability map for Asana project and task 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 workspace identity, task fi...Votes: 0GitHub stars: 2
- Asana Automation Change Impact AssessmentUse when a proposed Asana project and task workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Asana project and task 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 workspace identity, task ...Votes: 0GitHub stars: 2
- Asana Automation Failure Triage RecordUse when a reproducible Asana project and task workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Asana project and task 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 workspace identity, task fields, ownership references, due date...Votes: 0GitHub stars: 2
- Asana Automation Input Output ContractUse when the accepted inputs or produced outputs for Asana project and task workflows need a checkable boundary. Produce an input/output contract for Asana project and task 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 workspace identity, task fields, ownership references, ...Votes: 0GitHub stars: 2
- Asana Automation Integration Parity TraceUse when Asana project and task workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Asana project and task 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 workspace identity, task fields, ownership references, due dates, and bu...Votes: 0GitHub stars: 2
- Asana Automation Performance EnvelopeUse when Asana project and task workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Asana project and task 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 workspace identity, task fields, ownership re...Votes: 0GitHub stars: 2
- Asana Automation Permission Boundary ReviewUse when Asana project and task workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Asana project and task 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 workspace identity, task fields, o...Votes: 0GitHub stars: 2
- Asana Automation Release Handoff RecordUse when a Asana project and task workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Asana project and task 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 workspace identity, task fi...Votes: 0GitHub stars: 2
- Asana Automation Reproducibility Fixture PlanUse when a Asana project and task workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Asana project and task 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 bounded to...Votes: 0GitHub stars: 2
- Asana Automation Version CompatibilityUse when a Asana project and task workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Asana project and task 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 workspace identity, ta...Votes: 0GitHub stars: 2
- Basecamp Automation Capability Surface MapUse when the actual capability boundary of Basecamp project workflows needs to be distinguished from assumptions. Produce a capability map for Basecamp project 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 project and to-do identity, message att...Votes: 0GitHub stars: 2
- Basecamp Automation Change Impact AssessmentUse when a proposed Basecamp project workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Basecamp project 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 project and to-do identity, message a...Votes: 0GitHub stars: 2
- Basecamp Automation Failure Triage RecordUse when a reproducible Basecamp project workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Basecamp project 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 project and to-do identity, message attachments, notification boundary, and...Votes: 0GitHub stars: 2
- Basecamp Automation Input Output ContractUse when the accepted inputs or produced outputs for Basecamp project workflows need a checkable boundary. Produce an input/output contract for Basecamp project 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 project and to-do identity, message attachments, notification bound...Votes: 0GitHub stars: 2
- Basecamp Automation Integration Parity TraceUse when Basecamp project workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Basecamp project 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 project and to-do identity, message attachments, notification boundary, and status r...Votes: 0GitHub stars: 2
- Basecamp Automation Performance EnvelopeUse when Basecamp project workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Basecamp project 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 project and to-do identity, message attachments, notifica...Votes: 0GitHub stars: 2
- Basecamp Automation Permission Boundary ReviewUse when Basecamp project workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Basecamp project 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 project and to-do identity, message attachment...Votes: 0GitHub stars: 2
- Basecamp Automation Release Handoff RecordUse when a Basecamp project workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Basecamp project 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 project and to-do identity, message att...Votes: 0GitHub stars: 2
- Basecamp Automation Reproducibility Fixture PlanUse when a Basecamp project workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Basecamp project 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 bounded to project and...Votes: 0GitHub stars: 2
- Basecamp Automation Version CompatibilityUse when a Basecamp project workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Basecamp project 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 project and to-do identity, messag...Votes: 0GitHub stars: 2
- Calendar Agenda BriefingUse when a task involves preparing a concise calendar agenda briefing with meeting timezones, attendees, and relevant authorized documents to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external w...Votes: 0GitHub stars: 2
- Calendar Conflict AuditUse when a task involves checking a set of proposed calendar events for time conflicts, timezone errors, and attendee availability to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external writes or...Votes: 0GitHub stars: 2
- Confluence Automation Capability Surface MapUse when the actual capability boundary of Confluence page workflows needs to be distinguished from assumptions. Produce a capability map for Confluence page 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 space and page identity, hierarchy, versi...Votes: 0GitHub stars: 2
- Confluence Automation Change Impact AssessmentUse when a proposed Confluence page workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Confluence page 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 space and page identity, hierarchy, ver...Votes: 0GitHub stars: 2
- Confluence Automation Failure Triage RecordUse when a reproducible Confluence page workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Confluence page 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 space and page identity, hierarchy, version history, labels, and permission b...Votes: 0GitHub stars: 2
- Confluence Automation Input Output ContractUse when the accepted inputs or produced outputs for Confluence page workflows need a checkable boundary. Produce an input/output contract for Confluence page 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 space and page identity, hierarchy, version history, labels, and perm...Votes: 0GitHub stars: 2
- Confluence Automation Integration Parity TraceUse when Confluence page workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Confluence page 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 space and page identity, hierarchy, version history, labels, and permission boundary. ...Votes: 0GitHub stars: 2
- Confluence Automation Performance EnvelopeUse when Confluence page workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Confluence page 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 space and page identity, hierarchy, version history, labels...Votes: 0GitHub stars: 2
- Confluence Automation Permission Boundary ReviewUse when Confluence page workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Confluence page 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 space and page identity, hierarchy, version hist...Votes: 0GitHub stars: 2
- Confluence Automation Release Handoff RecordUse when a Confluence page workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Confluence page 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 space and page identity, hierarchy, versi...Votes: 0GitHub stars: 2