diff --git a/skills/zendesk-backlog-trend-analysis/references/shared-agent-rollout-checklist.md b/skills/zendesk-backlog-trend-analysis/references/shared-agent-rollout-checklist.md index 443f0a4254..25e3ac44e6 100644 --- a/skills/zendesk-backlog-trend-analysis/references/shared-agent-rollout-checklist.md +++ b/skills/zendesk-backlog-trend-analysis/references/shared-agent-rollout-checklist.md @@ -64,15 +64,3 @@ Review the skill when: - a new support workflow skill is added - agents receive new write permissions - repeated false positives appear in reports - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-backlog-trend-analysis/references/shared-agent-smoke-test-plan.md b/skills/zendesk-backlog-trend-analysis/references/shared-agent-smoke-test-plan.md index 562224d291..995953739a 100644 --- a/skills/zendesk-backlog-trend-analysis/references/shared-agent-smoke-test-plan.md +++ b/skills/zendesk-backlog-trend-analysis/references/shared-agent-smoke-test-plan.md @@ -56,5 +56,3 @@ The skill is ready for shared-agent rollout only when: ## Recording results Use `examples/smoke-test-results-template.md` to capture test results. Keep results outside the skill package when they include real ticket data. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-backlog-trend-analysis/references/workspace-capability-profile.md b/skills/zendesk-backlog-trend-analysis/references/workspace-capability-profile.md index 6c78d9d681..67ce551fbc 100644 --- a/skills/zendesk-backlog-trend-analysis/references/workspace-capability-profile.md +++ b/skills/zendesk-backlog-trend-analysis/references/workspace-capability-profile.md @@ -94,5 +94,3 @@ Review the profile when: - the team adds or removes Zendesk groups, brands, or forms Treat the profile as operational configuration, not memory. If it becomes outdated, prefer saying capability is uncertain and rerun the capability preflight. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-backlog-trend-analysis/references/zendesk-query-recipes.md b/skills/zendesk-backlog-trend-analysis/references/zendesk-query-recipes.md index 062d90764b..72f99ac20b 100644 --- a/skills/zendesk-backlog-trend-analysis/references/zendesk-query-recipes.md +++ b/skills/zendesk-backlog-trend-analysis/references/zendesk-query-recipes.md @@ -113,21 +113,3 @@ Return: - observed shared signals - classification: likely duplicate, related but distinct, repeated support pain, possible incident signal, or inconclusive - recommended support action - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-backlog-trend-analysis/templates/backlog-health-summary.md b/skills/zendesk-backlog-trend-analysis/templates/backlog-health-summary.md index 54dbfbe0d3..c22758cbfc 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/backlog-health-summary.md +++ b/skills/zendesk-backlog-trend-analysis/templates/backlog-health-summary.md @@ -74,21 +74,3 @@ Use this template for current open backlog or queue health reports. Omit empty s - Ticket details sampled: - Secondary sources used: - Missing evidence: - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-backlog-trend-analysis/templates/daily-digest.md b/skills/zendesk-backlog-trend-analysis/templates/daily-digest.md index cf3bac6acf..e8400a86e7 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/daily-digest.md +++ b/skills/zendesk-backlog-trend-analysis/templates/daily-digest.md @@ -67,21 +67,3 @@ Use this template for daily or weekday operational digests. - SLA data visible: - Ticket details sampled: - Missing evidence: - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-backlog-trend-analysis/templates/evidence-basis.md b/skills/zendesk-backlog-trend-analysis/templates/evidence-basis.md index f90ef83224..8e57bc09dc 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/evidence-basis.md +++ b/skills/zendesk-backlog-trend-analysis/templates/evidence-basis.md @@ -39,5 +39,3 @@ Use this section in every report. - Help Centre checked, if relevant: - Secondary sources used: - Missing or incomplete evidence: - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-backlog-trend-analysis/templates/repeated-theme-review.md b/skills/zendesk-backlog-trend-analysis/templates/repeated-theme-review.md index fbdd2cd657..4dec78c747 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/repeated-theme-review.md +++ b/skills/zendesk-backlog-trend-analysis/templates/repeated-theme-review.md @@ -68,15 +68,3 @@ Use this template when the request focuses on recurring symptoms, suspected dupl - Ticket details sampled: - SLA data visible: - Missing evidence: - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-backlog-trend-analysis/templates/shared-agent-installation-note.md b/skills/zendesk-backlog-trend-analysis/templates/shared-agent-installation-note.md index c2f075af4c..046ca27813 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/shared-agent-installation-note.md +++ b/skills/zendesk-backlog-trend-analysis/templates/shared-agent-installation-note.md @@ -76,21 +76,3 @@ Status: go / partial / no-go Required fixes before broader use: - - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-backlog-trend-analysis/templates/trend-comparison.md b/skills/zendesk-backlog-trend-analysis/templates/trend-comparison.md index 94b8b07bf8..42dba975c8 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/trend-comparison.md +++ b/skills/zendesk-backlog-trend-analysis/templates/trend-comparison.md @@ -77,21 +77,3 @@ Use this template for period-over-period backlog or support trend analysis. - SLA data visible: - Ticket details sampled: - Secondary sources used: - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-backlog-trend-analysis/templates/weekly-support-report.md b/skills/zendesk-backlog-trend-analysis/templates/weekly-support-report.md index 78f1bf47ea..64827e751f 100644 --- a/skills/zendesk-backlog-trend-analysis/templates/weekly-support-report.md +++ b/skills/zendesk-backlog-trend-analysis/templates/weekly-support-report.md @@ -76,5 +76,3 @@ Use this template for weekly support summaries. Omit empty sections and unsuppor - Ticket details sampled: - Secondary sources used: - Missing evidence: - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-bug-report-package/examples/bug-package-cases.md b/skills/zendesk-bug-report-package/examples/bug-package-cases.md index 3d40129618..dc29148b8f 100644 --- a/skills/zendesk-bug-report-package/examples/bug-package-cases.md +++ b/skills/zendesk-bug-report-package/examples/bug-package-cases.md @@ -178,21 +178,3 @@ Reason: this is refund/policy/customer communication work, not a defect package. Recommended destination/skill: use the relevant billing/policy workflow if available, or `zendesk-draft-response` if the user needs a customer-facing reply. Use `zendesk-customer-research` if prior commitments or account context matter. ``` - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-bug-report-package/examples/shared-agent-smoke-tests.md b/skills/zendesk-bug-report-package/examples/shared-agent-smoke-tests.md index 209cf8c3ce..17d7b49659 100644 --- a/skills/zendesk-bug-report-package/examples/shared-agent-smoke-tests.md +++ b/skills/zendesk-bug-report-package/examples/shared-agent-smoke-tests.md @@ -57,15 +57,3 @@ When intentionally invoking `zendesk-router-skill`, the router should return: **What input would help next:** The ticket URL or pasted support thread plus expected behaviour, actual behaviour, reproduction clues, impact, and any screenshots/logs. ``` - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-bug-report-package/references/memory-policy.md b/skills/zendesk-bug-report-package/references/memory-policy.md index e566e03fc8..887922e52e 100644 --- a/skills/zendesk-bug-report-package/references/memory-policy.md +++ b/skills/zendesk-bug-report-package/references/memory-policy.md @@ -72,21 +72,3 @@ Remember that a named customer had a checkout bug on a specific ticket caused by ## Relying on memory If durable memory exists, treat it as a starting convention, not case evidence. Case facts must still come from Zendesk or supplied evidence during the current run. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-bug-report-package/references/router-integration.md b/skills/zendesk-bug-report-package/references/router-integration.md index 3918b7fc9d..e7474c1814 100644 --- a/skills/zendesk-bug-report-package/references/router-integration.md +++ b/skills/zendesk-bug-report-package/references/router-integration.md @@ -58,21 +58,3 @@ Do not route here when the dominant need is first-pass classification, missing e ## Shared-agent fallback If Zendesk access is unavailable, the router should still recommend this skill when the intent is clearly defect packaging, but it must ask for the smallest useful pasted ticket/thread or investigation extract and avoid claiming live Zendesk evidence was inspected. - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-bug-report-package/references/routing-boundaries.md b/skills/zendesk-bug-report-package/references/routing-boundaries.md index f65a45b5a1..513dc26b00 100644 --- a/skills/zendesk-bug-report-package/references/routing-boundaries.md +++ b/skills/zendesk-bug-report-package/references/routing-boundaries.md @@ -87,21 +87,3 @@ Example: ```markdown This is better handled by `zendesk-customer-escalation` because the dominant issue is customer impact and urgent intervention, not defect packaging. Use the confirmed behaviour and reproduction clues below as supporting evidence for the escalation brief. ``` - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-bug-report-package/references/shared-agent-setup.md b/skills/zendesk-bug-report-package/references/shared-agent-setup.md index 115c47dbf8..ebad4fbdf9 100644 --- a/skills/zendesk-bug-report-package/references/shared-agent-setup.md +++ b/skills/zendesk-bug-report-package/references/shared-agent-setup.md @@ -71,21 +71,3 @@ When the issue should not become a bug package yet: ```markdown This is not ready for a bug package. The smallest useful next step is to collect [specific reproduction/environment/detail], then re-run the package workflow. ``` - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-bug-report-package/references/source-access-profile.md b/skills/zendesk-bug-report-package/references/source-access-profile.md index ed8389bac3..3c5528f3bb 100644 --- a/skills/zendesk-bug-report-package/references/source-access-profile.md +++ b/skills/zendesk-bug-report-package/references/source-access-profile.md @@ -49,5 +49,3 @@ Use supplied evidence, mark missing facts, and ask for the smallest next extract ## Redaction guidance Summarise sensitive evidence and link back to Zendesk or the authorised source when possible. Do not copy credentials, tokens, payment details, personal data, security-sensitive logs, or unnecessary raw payloads into a bug package. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-bug-report-package/templates/bug-package-template.md b/skills/zendesk-bug-report-package/templates/bug-package-template.md index ca1fd8b67f..f4b11f928f 100644 --- a/skills/zendesk-bug-report-package/templates/bug-package-template.md +++ b/skills/zendesk-bug-report-package/templates/bug-package-template.md @@ -99,5 +99,3 @@ Exact ask for recipient: - Do not claim scope yet: [unsupported scope claims] - Sensitive evidence omitted or linked in Zendesk: [yes/no/unknown] ``` - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-create-knowledge/references/article-templates.md b/skills/zendesk-create-knowledge/references/article-templates.md index 9f3a6a7ac9..fb027b832f 100644 --- a/skills/zendesk-create-knowledge/references/article-templates.md +++ b/skills/zendesk-create-knowledge/references/article-templates.md @@ -254,21 +254,3 @@ Use when an existing article should be updated rather than creating a new one. - Reviewer needed: - Public/internal boundary: ``` - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-create-knowledge/references/evidence-confidence-rubric.md b/skills/zendesk-create-knowledge/references/evidence-confidence-rubric.md index a6d0c1b37a..d0027395ea 100644 --- a/skills/zendesk-create-knowledge/references/evidence-confidence-rubric.md +++ b/skills/zendesk-create-knowledge/references/evidence-confidence-rubric.md @@ -135,21 +135,3 @@ Examples: - `zendesk-knowledge-candidate-review` β€” documentation value, audience, visibility, or stability is unclear - `zendesk-evidence-quality-review` β€” draft needs evidence, claims, boundary, or wording QA before sharing - `zendesk-customer-research` β€” customer/account context may change article scope or risk - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-create-knowledge/references/examples.md b/skills/zendesk-create-knowledge/references/examples.md index 75ae49d5b6..3c4c6a34a4 100644 --- a/skills/zendesk-create-knowledge/references/examples.md +++ b/skills/zendesk-create-knowledge/references/examples.md @@ -336,21 +336,3 @@ Escalate when: - Replace every placeholder with evidence from the current support case, article, or approved source. - Do not infer product status, affected audience, timelines, or root cause from examples. - Do not copy internal-only sections into public articles. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-create-knowledge/references/public-internal-boundary.md b/skills/zendesk-create-knowledge/references/public-internal-boundary.md index b7a258e7bb..57bc98c14e 100644 --- a/skills/zendesk-create-knowledge/references/public-internal-boundary.md +++ b/skills/zendesk-create-knowledge/references/public-internal-boundary.md @@ -181,5 +181,3 @@ Examples: ```md - Public/internal boundary: Needs review. The workaround appears temporary and product status is not confirmed. ``` - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-create-knowledge/references/routing-boundaries.md b/skills/zendesk-create-knowledge/references/routing-boundaries.md index 9087a5067e..089cbba09c 100644 --- a/skills/zendesk-create-knowledge/references/routing-boundaries.md +++ b/skills/zendesk-create-knowledge/references/routing-boundaries.md @@ -102,21 +102,3 @@ Recommended next route: `` β€” ``` - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-draft-response/references/shared-agent-installation-checklist.md b/skills/zendesk-draft-response/references/shared-agent-installation-checklist.md index a7931e7a9c..3412574674 100644 --- a/skills/zendesk-draft-response/references/shared-agent-installation-checklist.md +++ b/skills/zendesk-draft-response/references/shared-agent-installation-checklist.md @@ -80,21 +80,3 @@ Before treating the shared agent as ready, test these cases: - [ ] `templates/redacted-support-context-template.md` is available for approved redacted fixtures. - [ ] `scripts/redact_context.py` has been tested on one synthetic sample with an email, URL, ticket ID, and custom customer/account mapping. - [ ] The team understands that sensitive security, payment, credential, or personal-data cases should usually be rewritten synthetically rather than stored as redacted examples. - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-draft-response/references/shared-agent-regression-tests.md b/skills/zendesk-draft-response/references/shared-agent-regression-tests.md index bcf43ea0ac..e1f8e4b830 100644 --- a/skills/zendesk-draft-response/references/shared-agent-regression-tests.md +++ b/skills/zendesk-draft-response/references/shared-agent-regression-tests.md @@ -154,5 +154,3 @@ Pass if the redacted prompt is useful for testing but no longer identifies a rea ## Router Boundary Smoke Test Include a prompt that asks `zendesk-draft-response` to choose between multiple Zendesk workflows. Expected behaviour: return to `zendesk-router-skill`, do not draft a reply, and do not present a broad Zendesk skill menu. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-draft-response/references/shared-agent-setup.md b/skills/zendesk-draft-response/references/shared-agent-setup.md index b3839e4bdb..520687d305 100644 --- a/skills/zendesk-draft-response/references/shared-agent-setup.md +++ b/skills/zendesk-draft-response/references/shared-agent-setup.md @@ -70,21 +70,3 @@ After configuring this skill in a shared agent, use `references/shared-agent-reg Before adding support context to shared instructions, examples, smoke tests, QA fixtures, or documentation, read `references/data-redaction-rules.md` and use `templates/redacted-support-context-template.md` when structure is needed. Run `scripts/redact_context.py` for a deterministic first pass, then manually review the result. Do not store real customer evidence, private URLs, ticket IDs, screenshots, credentials, payment details, security findings, or personal contact details in the skill package or shared Memory. Use synthetic examples when redaction would make the case unclear or when the source includes sensitive security, payment, or identity data. - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-draft-response/references/tone-playbook.md b/skills/zendesk-draft-response/references/tone-playbook.md index 87cc789e41..05181ce976 100644 --- a/skills/zendesk-draft-response/references/tone-playbook.md +++ b/skills/zendesk-draft-response/references/tone-playbook.md @@ -76,21 +76,3 @@ Avoid: ## Technical Customers Use precise wording, but do not overload the reply. Include steps, constraints, affected areas, and validation details only when they help the customer act. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-draft-response/templates/CONNECTORS.example.md b/skills/zendesk-draft-response/templates/CONNECTORS.example.md index db3a015f4b..9b7180b17f 100644 --- a/skills/zendesk-draft-response/templates/CONNECTORS.example.md +++ b/skills/zendesk-draft-response/templates/CONNECTORS.example.md @@ -61,5 +61,3 @@ Copy this file into the shared agent's persistent instructions or shared files a - If Slack is unavailable, do not invent internal context or owner confirmation. - If evidence is incomplete, use the smallest safe clarification or route to evidence collection. - Never include private connector IDs, credentials, API tokens, or personal mailbox details in skill files. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-draft-response/templates/customer-reply-template.md b/skills/zendesk-draft-response/templates/customer-reply-template.md index 850213c8b7..0c40af6b35 100644 --- a/skills/zendesk-draft-response/templates/customer-reply-template.md +++ b/skills/zendesk-draft-response/templates/customer-reply-template.md @@ -40,21 +40,3 @@ One or two sentences for the support agent. State the latest customer ask, the r - Source limitations: - Follow-up owner or next action: - Escalation or QA recommendation: - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-draft-response/templates/redacted-support-context-template.md b/skills/zendesk-draft-response/templates/redacted-support-context-template.md index e4729bbe8a..8c7fca45ed 100644 --- a/skills/zendesk-draft-response/templates/redacted-support-context-template.md +++ b/skills/zendesk-draft-response/templates/redacted-support-context-template.md @@ -71,21 +71,3 @@ Issue summary: [short description of behaviour] - Real names replaced with generic placeholders. - Private URLs, IDs, contact details, credentials, and tokens removed or replaced. - Support meaning preserved without customer-identifying details. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-draft-response/templates/reply-only-template.md b/skills/zendesk-draft-response/templates/reply-only-template.md index 40998df1d6..608f6f857d 100644 --- a/skills/zendesk-draft-response/templates/reply-only-template.md +++ b/skills/zendesk-draft-response/templates/reply-only-template.md @@ -28,5 +28,3 @@ Use this template only when the user explicitly asks for the sendable reply text without internal notes. [Copy-paste-ready customer-facing reply only.] - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-draft-response/tests/shared-agent-smoke-prompts.md b/skills/zendesk-draft-response/tests/shared-agent-smoke-prompts.md index c7f52e60e7..d4950896f8 100644 --- a/skills/zendesk-draft-response/tests/shared-agent-smoke-prompts.md +++ b/skills/zendesk-draft-response/tests/shared-agent-smoke-prompts.md @@ -90,20 +90,5 @@ Use the Zendesk Draft Response skill. We have a vague Zendesk issue summary, pos Expected outcome: returns to `zendesk-router-skill`; does not draft a reply and does not present a broad menu of Zendesk skills. -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - _This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ [Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-evidence-collector/SKILL.md b/skills/zendesk-evidence-collector/SKILL.md index 00e339f2cc..a61d4d59a4 100644 --- a/skills/zendesk-evidence-collector/SKILL.md +++ b/skills/zendesk-evidence-collector/SKILL.md @@ -334,14 +334,4 @@ Investigation mode: - "Check whether this is already a known issue or a new failure pattern." - "Look up the current status and owner from the case evidence." -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - _Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-collector/examples/README.md b/skills/zendesk-evidence-collector/examples/README.md index 7f81711ca6..3030059df9 100644 --- a/skills/zendesk-evidence-collector/examples/README.md +++ b/skills/zendesk-evidence-collector/examples/README.md @@ -28,5 +28,3 @@ These examples are fictional and safe for shared-agent use. Use them as behavioural references only when the agent needs a pattern for handling common Zendesk evidence-collection or investigation situations. Do not treat names, ticket numbers, organisations, domains, timestamps, product details, or symptoms in these examples as real case evidence. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-evidence-collector/examples/evidence-pack-partially-ready.md b/skills/zendesk-evidence-collector/examples/evidence-pack-partially-ready.md index 0188834f98..fd24523bfb 100644 --- a/skills/zendesk-evidence-collector/examples/evidence-pack-partially-ready.md +++ b/skills/zendesk-evidence-collector/examples/evidence-pack-partially-ready.md @@ -81,15 +81,3 @@ Use evidence pack mode. Search for the tightest relevant ticket set, shortlist o - Supporting workflow: none - Note: if event-time proof becomes required, continue inside this skill's investigation mode before routing away - Immediate next action: Confirm ticket 73984 is the target and collect the smallest missing checkout identifiers before escalation. - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-collector/examples/evidence-pack-ready.md b/skills/zendesk-evidence-collector/examples/evidence-pack-ready.md index 12811a8fc3..bf75873aef 100644 --- a/skills/zendesk-evidence-collector/examples/evidence-pack-ready.md +++ b/skills/zendesk-evidence-collector/examples/evidence-pack-ready.md @@ -79,21 +79,3 @@ Use evidence pack mode. Do not investigate beyond Zendesk because the case is al - Primary workflow: zendesk-draft-response - Supporting workflow: none - Immediate next action: Draft a customer-safe reply explaining the next image recovery or re-sync step based only on confirmed ticket evidence. - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-evidence-collector/examples/investigation-blocked-event-time.md b/skills/zendesk-evidence-collector/examples/investigation-blocked-event-time.md index 69b0c33ae3..2f7e1c5f1e 100644 --- a/skills/zendesk-evidence-collector/examples/investigation-blocked-event-time.md +++ b/skills/zendesk-evidence-collector/examples/investigation-blocked-event-time.md @@ -83,15 +83,3 @@ The duplicate-charge claim is not proven or disproven from the available evidenc - Zendesk conversation for customer claim and screenshot context. - Current order/account state for present order count. - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-collector/examples/zendesk-unavailable-pasted-thread-only.md b/skills/zendesk-evidence-collector/examples/zendesk-unavailable-pasted-thread-only.md index e86dbed4d3..87a54ebd78 100644 --- a/skills/zendesk-evidence-collector/examples/zendesk-unavailable-pasted-thread-only.md +++ b/skills/zendesk-evidence-collector/examples/zendesk-unavailable-pasted-thread-only.md @@ -80,21 +80,3 @@ Be transparent that Zendesk was unavailable. Work only from supplied evidence. D - Primary workflow: zendesk-case-readiness-check - Supporting workflow: none - Immediate next action: Ask for the ticket ID or the smallest missing reproduction details before creating an escalation brief. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-evidence-collector/references/routing-boundaries.md b/skills/zendesk-evidence-collector/references/routing-boundaries.md index a0e8305c3e..67f772144a 100644 --- a/skills/zendesk-evidence-collector/references/routing-boundaries.md +++ b/skills/zendesk-evidence-collector/references/routing-boundaries.md @@ -91,5 +91,3 @@ In this skill's outputs, avoid long routing menus. The `Best next move` or `Reco - one primary workflow when clear; - one supporting workflow at most; - or a clear return to `zendesk-router-skill` when routing needs network-level judgement. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-evidence-collector/references/shared-agent-compatibility.md b/skills/zendesk-evidence-collector/references/shared-agent-compatibility.md index 9352a76a6b..016f4eaeaf 100644 --- a/skills/zendesk-evidence-collector/references/shared-agent-compatibility.md +++ b/skills/zendesk-evidence-collector/references/shared-agent-compatibility.md @@ -100,15 +100,3 @@ Use wording close to this when relevant: For a non-material secondary connector gap: > Zendesk has enough evidence for the next support step. The secondary source was not available, but that does not block the recommended workflow. - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-collector/references/shared-agent-defaults.md b/skills/zendesk-evidence-collector/references/shared-agent-defaults.md index 610abd2866..5c144d043f 100644 --- a/skills/zendesk-evidence-collector/references/shared-agent-defaults.md +++ b/skills/zendesk-evidence-collector/references/shared-agent-defaults.md @@ -109,21 +109,3 @@ Prefer customer-safe language that states what was checked, what is known, what - Keep evidence pack mode compact. - Keep investigation mode branch-led and focused on one active issue. - End with one concrete immediate next action. - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -*Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team* -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) - -_Maintained with ❀️ by the πŸš€ LightSpeedWP Automation Team_ -[Org Profile](https://github.com/lightspeedwp/.github/tree/main/profile) diff --git a/skills/zendesk-evidence-collector/references/source-precedence-examples.md b/skills/zendesk-evidence-collector/references/source-precedence-examples.md index cca49f7363..1cafc3b399 100644 --- a/skills/zendesk-evidence-collector/references/source-precedence-examples.md +++ b/skills/zendesk-evidence-collector/references/source-precedence-examples.md @@ -196,15 +196,3 @@ Use these patterns when evidence is partial: - "Inferred, not confirmed: ..." - "Disproven for the checked identifier: ..." - "Blocked until is checked: ..." - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-collector/templates/evidence-pack.md b/skills/zendesk-evidence-collector/templates/evidence-pack.md index ad8013970a..0f6bab0445 100644 --- a/skills/zendesk-evidence-collector/templates/evidence-pack.md +++ b/skills/zendesk-evidence-collector/templates/evidence-pack.md @@ -125,5 +125,3 @@ Use this variant when the user gives a customer or account name and there is not - Use missing or uncertain evidence for blockers, contradictions, connector limits, or unavailable Zendesk access. - Recommend one primary workflow only, using a canonical `zendesk-` name when routing away. - Do not add customer-facing wording unless the user explicitly asks for a reply draft. - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-evidence-collector/templates/investigation-report.md b/skills/zendesk-evidence-collector/templates/investigation-report.md index 4ea2af9ee7..6fc8c5302e 100644 --- a/skills/zendesk-evidence-collector/templates/investigation-report.md +++ b/skills/zendesk-evidence-collector/templates/investigation-report.md @@ -79,21 +79,3 @@ Keep the investigation focused on one active issue. Every critical branch should - Do not declare `Confirmed root cause`, `Proven`, or `Disproven` unless the branch ledger supports it. - Do not invent request IDs, user IDs, account impact, reproduction steps, ownership, or ETA. - End with one recommended next action, not a broad task list. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-evidence-quality-review/examples/backlog-summary-review-example.md b/skills/zendesk-evidence-quality-review/examples/backlog-summary-review-example.md index ede0d4cc90..3becc3b8d3 100644 --- a/skills/zendesk-evidence-quality-review/examples/backlog-summary-review-example.md +++ b/skills/zendesk-evidence-quality-review/examples/backlog-summary-review-example.md @@ -77,21 +77,3 @@ Not ready. The backlog increase is supported by the supplied counts, but the cau - Next steps are specific and owned: Partially - Risk or escalation gaps remain: Yes - Safe to send or share as-is: No - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-evidence-quality-review/examples/customer-reply-review-example.md b/skills/zendesk-evidence-quality-review/examples/customer-reply-review-example.md index 2a307743d3..ed8514cb2f 100644 --- a/skills/zendesk-evidence-quality-review/examples/customer-reply-review-example.md +++ b/skills/zendesk-evidence-quality-review/examples/customer-reply-review-example.md @@ -78,15 +78,3 @@ Not ready. The reply includes unsupported root cause, engineering, timing, credi - Next steps are specific and owned: Partially - Risk or escalation gaps remain: Yes - Safe to send or share as-is: No - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_ diff --git a/skills/zendesk-evidence-quality-review/examples/escalation-review-example.md b/skills/zendesk-evidence-quality-review/examples/escalation-review-example.md index 320023c2b1..d680d2ff3a 100644 --- a/skills/zendesk-evidence-quality-review/examples/escalation-review-example.md +++ b/skills/zendesk-evidence-quality-review/examples/escalation-review-example.md @@ -75,21 +75,3 @@ Escalation could be appropriate because the customer reports a blocked campaign - Target owner or team is clear: No - Exact ask is actionable: No - Safe to escalate as-is: No - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-evidence-quality-review/examples/knowledge-draft-review-example.md b/skills/zendesk-evidence-quality-review/examples/knowledge-draft-review-example.md index 5b5b414a8c..8ccd6202fb 100644 --- a/skills/zendesk-evidence-quality-review/examples/knowledge-draft-review-example.md +++ b/skills/zendesk-evidence-quality-review/examples/knowledge-draft-review-example.md @@ -72,5 +72,3 @@ The issue and workaround are confirmed only for one customer. The cause, scope, - Scope and exclusions are clear: No - Safe for public help centre: No - Better kept internal for now: Yes - -*Have questions? Ping us on GitHub! πŸ™ Made with πŸ’š by LightSpeedWP* diff --git a/skills/zendesk-evidence-quality-review/examples/privacy-redaction-review-example.md b/skills/zendesk-evidence-quality-review/examples/privacy-redaction-review-example.md index 51a40354e1..eaf6224066 100644 --- a/skills/zendesk-evidence-quality-review/examples/privacy-redaction-review-example.md +++ b/skills/zendesk-evidence-quality-review/examples/privacy-redaction-review-example.md @@ -74,21 +74,3 @@ Replace the customer-facing paragraph with: ## Why this is correct The review keeps the useful support signal while removing unnecessary personal data, secrets, other-customer references, internal speculation, and unsupported delivery commitments. - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-evidence-quality-review/examples/review-severity-calibration-cases.md b/skills/zendesk-evidence-quality-review/examples/review-severity-calibration-cases.md index 8308db7370..f7c7adb8de 100644 --- a/skills/zendesk-evidence-quality-review/examples/review-severity-calibration-cases.md +++ b/skills/zendesk-evidence-quality-review/examples/review-severity-calibration-cases.md @@ -152,21 +152,3 @@ One customer’s issue was resolved with this workaround. No confirmation exists ### Safer replacement β€œInternal note: this workaround resolved one reported case. Verify affected versions, scope, and side effects before publishing customer-facing guidance.” - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -*Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!* -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) - -_Built by 🧱 LightSpeedWP with β˜•, πŸš€, and open-source spirit!_ -[Contributors](https://github.com/lightspeedwp/lsx-demo-theme/graphs/contributors) diff --git a/skills/zendesk-evidence-quality-review/examples/routing-boundary-cases.md b/skills/zendesk-evidence-quality-review/examples/routing-boundary-cases.md index 289d213406..e45d58511f 100644 --- a/skills/zendesk-evidence-quality-review/examples/routing-boundary-cases.md +++ b/skills/zendesk-evidence-quality-review/examples/routing-boundary-cases.md @@ -226,21 +226,3 @@ Use `zendesk-evidence-quality-review` cautiously if the handoff draft and summar ### Reason A reviewable artefact exists, but evidence is indirect. Label findings as based on the supplied summary and avoid treating the summary as confirmed Zendesk evidence. - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -*This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP.* -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) - -_This page brought to you by the πŸ¦„ Magic Automation Unicorns of LightSpeedWP._ -[Automation Docs](https://github.com/lightspeedwp/.github/tree/main/instructions) diff --git a/skills/zendesk-evidence-quality-review/examples/shared-agent-acceptance-test-fixtures.md b/skills/zendesk-evidence-quality-review/examples/shared-agent-acceptance-test-fixtures.md index 5896ad4f2e..518e90e269 100644 --- a/skills/zendesk-evidence-quality-review/examples/shared-agent-acceptance-test-fixtures.md +++ b/skills/zendesk-evidence-quality-review/examples/shared-agent-acceptance-test-fixtures.md @@ -110,15 +110,3 @@ CSV imports fail above 500 rows. Split all import files into 500-row batches to ``` Expected: flag as not ready for public documentation; recommend internal-only note or further verification. - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -*Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!* - -_Docs signed by πŸ€– Copilot for LightSpeedWP – always fresh!_