All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Devrel Quickstart Friction Threshold Rule CheckUse when a developer quickstart friction analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the quickstart friction map 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Approval Evidence PacketUse when a sample repository release synchronization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Change Impact TraceUse when a version, rule, source, or stakeholder change may affect sample repository release synchronization to produce a before/after change record and impact map for the sample-repository version map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Closeout Handoff LedgerUse when a sample repository release synchronization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Completeness ReconciliationUse when the sample repository release synchronization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Exception Triage QueueUse when the sample repository release synchronization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Recovery Readiness DrillUse when the sample repository release synchronization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Scenario Sensitivity MatrixUse when the sample repository release synchronization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sample-repository version map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Scope Intake GateUse when a new sample repository release synchronization request needs a bounded work scope to produce a scoped intake card for the sample-repository version map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Source Provenance LedgerUse when a decision about sample repository release synchronization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sample-repository version map. Success means each material claim has a source, version/date, location, and confidence note; the sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Aas Devrel Sample Repo Sync Threshold Rule CheckUse when a sample repository release synchronization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sample-repository version map 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 sample identifies its supported release and outdated code paths are listed. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Approval Evidence PacketUse when a developer sample credential hygiene result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search,...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer sample credential hygiene to produce a before/after change record and impact map for the sample credential hygiene report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Closeout Handoff LedgerUse when a developer sample credential hygiene work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Completeness ReconciliationUse when the developer sample credential hygiene workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Exception Triage QueueUse when the developer sample credential hygiene workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Recovery Readiness DrillUse when the developer sample credential hygiene workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Scenario Sensitivity MatrixUse when the developer sample credential hygiene team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sample credential hygiene report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Scope Intake GateUse when a new developer sample credential hygiene request needs a bounded work scope to produce a scoped intake card for the sample credential hygiene report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Source Provenance LedgerUse when a decision about developer sample credential hygiene depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sample credential hygiene report. Success means each material claim has a source, version/date, location, and confidence note; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Aas Devrel Sample Secret Scan Threshold Rule CheckUse when a developer sample credential hygiene decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sample credential hygiene report 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; examples use nonfunctional placeholders and detected credential-like values are escalated. Use configured search, fe...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Approval Evidence PacketUse when a SDK example compilation verification result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Change Impact TraceUse when a version, rule, source, or stakeholder change may affect SDK example compilation verification to produce a before/after change record and impact map for the SDK example verification matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Closeout Handoff LedgerUse when a SDK example compilation verification work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Completeness ReconciliationUse when the SDK example compilation verification workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Exception Triage QueueUse when the SDK example compilation verification workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Recovery Readiness DrillUse when the SDK example compilation verification workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Scenario Sensitivity MatrixUse when the SDK example compilation verification team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the SDK example verification matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Scope Intake GateUse when a new SDK example compilation verification request needs a bounded work scope to produce a scoped intake card for the SDK example verification matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; examples compile or execute in an isolated sandbox without embedded credentials. 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 Devrel Sdk Example Build Source Provenance LedgerUse when a decision about SDK example compilation verification depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the SDK example verification matrix. Success means each material claim has a source, version/date, location, and confidence note; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Aas Devrel Sdk Example Build Threshold Rule CheckUse when a SDK example compilation verification decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the SDK example verification matrix 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; examples compile or execute in an isolated sandbox without embedded credentials. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Approval Evidence PacketUse when a developer support theme synthesis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer support theme synthesis to produce a before/after change record and impact map for the support-theme evidence table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Closeout Handoff LedgerUse when a developer support theme synthesis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Completeness ReconciliationUse when the developer support theme synthesis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Exception Triage QueueUse when the developer support theme synthesis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Recovery Readiness DrillUse when the developer support theme synthesis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Scenario Sensitivity MatrixUse when the developer support theme synthesis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the support-theme evidence table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Scope Intake GateUse when a new developer support theme synthesis request needs a bounded work scope to produce a scoped intake card for the support-theme evidence table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Source Provenance LedgerUse when a decision about developer support theme synthesis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the support-theme evidence table. Success means each material claim has a source, version/date, location, and confidence note; each theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Devrel Support Signal Threshold Rule CheckUse when a developer support theme synthesis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the support-theme evidence table 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 theme is traceable to de-identified evidence and volume limits are explicit. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Approval Evidence PacketUse when a technical tutorial prerequisite accuracy result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the tutorial prerequisite verification sheet 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 prerequisite list is sufficient for the described first result in a fresh test. Use configured s...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Change Impact TraceUse when a version, rule, source, or stakeholder change may affect technical tutorial prerequisite accuracy to produce a before/after change record and impact map for the tutorial prerequisite verification sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Closeout Handoff LedgerUse when a technical tutorial prerequisite accuracy work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the tutorial prerequisite verification sheet 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 prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Completeness ReconciliationUse when the technical tutorial prerequisite accuracy workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the tutorial prerequisite verification sheet 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 prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fe...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Exception Triage QueueUse when the technical tutorial prerequisite accuracy workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the tutorial prerequisite verification sheet 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 prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Recovery Readiness DrillUse when the technical tutorial prerequisite accuracy workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the tutorial prerequisite verification sheet 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 prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetc...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Scenario Sensitivity MatrixUse when the technical tutorial prerequisite accuracy team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the tutorial prerequisite verification sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Scope Intake GateUse when a new technical tutorial prerequisite accuracy request needs a bounded work scope to produce a scoped intake card for the tutorial prerequisite verification sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Aas Devrel Tutorial Prerequisites Source Provenance LedgerUse when a decision about technical tutorial prerequisite accuracy depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the tutorial prerequisite verification sheet. Success means each material claim has a source, version/date, location, and confidence note; the prerequisite list is sufficient for the described first result in a fresh test. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2