All authors

Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Docs Ocr Confidence Approval Evidence PacketUse when a OCR confidence exception handling result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Change Impact TraceUse when a version, rule, source, or stakeholder change may affect OCR confidence exception handling to produce a before/after change record and impact map for the OCR exception review queue. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Closeout Handoff LedgerUse when a OCR confidence exception handling work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Completeness ReconciliationUse when the OCR confidence exception handling workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Exception Triage QueueUse when the OCR confidence exception handling workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Recovery Readiness DrillUse when the OCR confidence exception handling workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Scenario Sensitivity MatrixUse when the OCR confidence exception handling team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the OCR exception review queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Scope Intake GateUse when a new OCR confidence exception handling request needs a bounded work scope to produce a scoped intake card for the OCR exception review queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; low-confidence regions are queued for review rather than silently treated as exact text. 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 Docs Ocr Confidence Source Provenance LedgerUse when a decision about OCR confidence exception handling depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the OCR exception review queue. Success means each material claim has a source, version/date, location, and confidence note; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Aas Docs Ocr Confidence Threshold Rule CheckUse when a OCR confidence exception handling decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the OCR exception review queue 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; low-confidence regions are queued for review rather than silently treated as exact text. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Approval Evidence PacketUse when a PDF form field integrity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the PDF form-field validation 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Change Impact TraceUse when a version, rule, source, or stakeholder change may affect PDF form field integrity to produce a before/after change record and impact map for the PDF form-field validation sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Closeout Handoff LedgerUse when a PDF form field integrity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the PDF form-field validation 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Completeness ReconciliationUse when the PDF form field integrity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the PDF form-field validation 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Exception Triage QueueUse when the PDF form field integrity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the PDF form-field validation 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Recovery Readiness DrillUse when the PDF form field integrity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the PDF form-field validation 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Scenario Sensitivity MatrixUse when the PDF form field integrity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the PDF form-field validation sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Scope Intake GateUse when a new PDF form field integrity request needs a bounded work scope to produce a scoped intake card for the PDF form-field validation sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; expected fields accept valid inputs and preserve values through the approved export path. 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
- Aas Docs Pdf Form Fields Source Provenance LedgerUse when a decision about PDF form field integrity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the PDF form-field validation sheet. Success means each material claim has a source, version/date, location, and confidence note; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Aas Docs Pdf Form Fields Threshold Rule CheckUse when a PDF form field integrity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the PDF form-field validation sheet 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; expected fields accept valid inputs and preserve values through the approved export path. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Approval Evidence PacketUse when a PDF structure tagging quality result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Change Impact TraceUse when a version, rule, source, or stakeholder change may affect PDF structure tagging quality to produce a before/after change record and impact map for the tagged-PDF structure review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Closeout Handoff LedgerUse when a PDF structure tagging quality work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Completeness ReconciliationUse when the PDF structure tagging quality workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Exception Triage QueueUse when the PDF structure tagging quality workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Recovery Readiness DrillUse when the PDF structure tagging quality workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Scenario Sensitivity MatrixUse when the PDF structure tagging quality team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the tagged-PDF structure review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Scope Intake GateUse when a new PDF structure tagging quality request needs a bounded work scope to produce a scoped intake card for the tagged-PDF structure review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; assistive navigation follows the intended structure and untagged content is localized. 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 Docs Pdf Tagging Source Provenance LedgerUse when a decision about PDF structure tagging quality depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the tagged-PDF structure review. Success means each material claim has a source, version/date, location, and confidence note; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Docs Pdf Tagging Threshold Rule CheckUse when a PDF structure tagging quality decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the tagged-PDF structure review 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; assistive navigation follows the intended structure and untagged content is localized. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Approval Evidence PacketUse when a document redaction verification result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the redaction verification 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Change Impact TraceUse when a version, rule, source, or stakeholder change may affect document redaction verification to produce a before/after change record and impact map for the redaction verification record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Closeout Handoff LedgerUse when a document redaction verification work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the redaction verification record 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Completeness ReconciliationUse when the document redaction verification workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the redaction verification record 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Exception Triage QueueUse when the document redaction verification workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the redaction verification record 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Recovery Readiness DrillUse when the document redaction verification workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the redaction verification record 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Scenario Sensitivity MatrixUse when the document redaction verification team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the redaction verification record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Scope Intake GateUse when a new document redaction verification request needs a bounded work scope to produce a scoped intake card for the redaction verification record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; restricted text cannot be recovered from the test export or its embedded metadata. 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 Docs Redaction Verification Source Provenance LedgerUse when a decision about document redaction verification depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the redaction verification record. Success means each material claim has a source, version/date, location, and confidence note; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Docs Redaction Verification Threshold Rule CheckUse when a document redaction verification decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the redaction verification record 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; restricted text cannot be recovered from the test export or its embedded metadata. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Approval Evidence PacketUse when a document signature metadata packaging result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configur...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Change Impact TraceUse when a version, rule, source, or stakeholder change may affect document signature metadata packaging to produce a before/after change record and impact map for the signature-package completeness list. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Closeout Handoff LedgerUse when a document signature metadata packaging work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Completeness ReconciliationUse when the document signature metadata packaging workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configured search...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Exception Triage QueueUse when the document signature metadata packaging workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Recovery Readiness DrillUse when the document signature metadata packaging workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configured search, ...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Scenario Sensitivity MatrixUse when the document signature metadata packaging team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the signature-package completeness list with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Scope Intake GateUse when a new document signature metadata packaging request needs a bounded work scope to produce a scoped intake card for the signature-package completeness list. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Source Provenance LedgerUse when a decision about document signature metadata packaging depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the signature-package completeness list. Success means each material claim has a source, version/date, location, and confidence note; the package identifies what was signed and verification state without asserting legal validity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and...Votes: 0GitHub stars: 2
- Aas Docs Signature Metadata Threshold Rule CheckUse when a document signature metadata packaging decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the signature-package completeness list 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 package identifies what was signed and verification state without asserting legal validity. Use configured ...Votes: 0GitHub stars: 2