How do I install the Wayland Support Week Batch skill?

Run npx skillmds@latest add ferroxlabs/wayland-support-week-batch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wayland Support Week Batch safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wayland Support Week Batch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wayland Support Week Batch free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Wayland Support Week Batch?

FerroxLabs (@ferroxlabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wayland Support Week Batch by ferroxlabs

Name: Wayland Support Week Batch
Author: FerroxLabs

Wayland Support Week Batch

Run the weekly support batch deterministically: pull weekly metrics, check SLA compliance, and detect recurring patterns across the week's tickets in one pass. Use when the user wants an automated, multi-step weekly support roll-up from a ticket export, producing metrics, an SLA-compliance status, and detected patterns. Do NOT use for triaging a single live ticket or answering one ad-hoc support question that one atomic skill can answer.

FerroxLabs e9c99fe 3.0 KB Updated Sep 17, 2026 37 repo stars

File contents

Weekly Support Batch

Estimated time: about 60 seconds

This workflow runs a deterministic weekly support roll-up in three steps: pull weekly metrics, run an SLA-compliance check, and detect recurring patterns. It is not interactive; the agent executes each step in order and assembles the output.

Data input: the user provides tickets_dir, a path to an attached or exported ticket file (CSV / PDF / XLSX) in the workspace. If no export is available, pull from the connected Intercom or HubSpot tickets connector. If neither a file nor a connector exists, ask the user to attach the export rather than inventing data. The user may optionally provide sla_targets_path, a path to SLA target definitions.

Steps

Step 1: Pull Weekly Metrics (uses: support-report)

Using the support-report skill in weekly-pull mode, read the ticket export at tickets_dir (or the connected Intercom/HubSpot connector if no file is given) and compute the week's support metrics: volume, response and resolution times, backlog, and any other standard weekly figures the skill produces. Capture the metrics. This step is required: if it cannot read any ticket source, halt and ask the user to attach the export rather than continuing with invented data.

Input: tickets_dir (or connected tickets connector)
Output: metrics
Key focus: this step gates the others; halt on error rather than fabricating data

Step 2: SLA Compliance Check (uses: support-sla-review)

Using the support-sla-review skill with the metrics from Step 1 and the optional sla_targets_path, check SLA compliance for the week and produce an SLA status (which targets were met or breached, and by how much). Capture the SLA status. If this step fails, skip it and continue to Step 3; record that the SLA status is unavailable.

Input: metrics from Step 1, sla_targets_path (optional)
Output: SLA status
Key focus: compare actuals to targets; skip gracefully if no targets are defined

Step 3: Detect Recurring Patterns (uses: support-faq)

Using the support-faq skill in weekly-pattern-detection mode, scan the same tickets_dir source and detect recurring themes and patterns across the week's tickets. Capture the patterns. If this step fails, skip it and continue; record that pattern detection is unavailable. Assemble the final output with three sections: Metrics, SLA Status, Patterns.

Input: tickets_dir (or connected tickets connector)
Output: patterns, assembled weekly output (Metrics, SLA Status, Patterns)
Key focus: surface the week's recurring themes; skip gracefully on error

---name: wayland-support-week-batchdescription: Run the weekly support batch deterministically: pull weekly metrics, check SLA compliance, and detect recurring patterns across the week's tickets in one pass. Use when the user wants an automated, multi-step weekly support roll-up from a ticket export, producing metrics, an SLA-compliance status, and detected patterns. Do NOT use for triaging a single live ticket or answering one ad-hoc support question that one atomic skill can answer.license: Apache-2.0---# Weekly Support Batch**Estimated time:** about 60 secondsThis workflow runs a deterministic weekly support roll-up in three steps: pullweekly metrics, run an SLA-compliance check, and detect recurring patterns. It isnot interactive; the agent executes each step in order and assembles the output.**Data input:** the user provides `tickets_dir`, a path to an attached or exportedticket file (CSV / PDF / XLSX) in the workspace. If no export is available, pullfrom the connected Intercom or HubSpot tickets connector. If neither a file nor aconnector exists, ask the user to attach the export rather than inventing data.The user may optionally provide `sla_targets_path`, a path to SLA targetdefinitions.## Steps**Step 1: Pull Weekly Metrics** (uses: support-report)Using the support-report skill in weekly-pull mode, read the ticket export at`tickets_dir` (or the connected Intercom/HubSpot connector if no file is given)and compute the week's support metrics: volume, response and resolution times,backlog, and any other standard weekly figures the skill produces. Capture themetrics. This step is required: if it cannot read any ticket source, halt and askthe user to attach the export rather than continuing with invented data.- Input: tickets_dir (or connected tickets connector)- Output: metrics- Key focus: this step gates the others; halt on error rather than fabricating data**Step 2: SLA Compliance Check** (uses: support-sla-review)Using the support-sla-review skill with the metrics from Step 1 and the optional`sla_targets_path`, check SLA compliance for the week and produce an SLA status(which targets were met or breached, and by how much). Capture the SLA status. Ifthis step fails, skip it and continue to Step 3; record that the SLA status isunavailable.- Input: metrics from Step 1, sla_targets_path (optional)- Output: SLA status- Key focus: compare actuals to targets; skip gracefully if no targets are defined**Step 3: Detect Recurring Patterns** (uses: support-faq)Using the support-faq skill in weekly-pattern-detection mode, scan the same`tickets_dir` source and detect recurring themes and patterns across the week'stickets. Capture the patterns. If this step fails, skip it and continue; recordthat pattern detection is unavailable. Assemble the final output with threesections: Metrics, SLA Status, Patterns.- Input: tickets_dir (or connected tickets connector)- Output: patterns, assembled weekly output (Metrics, SLA Status, Patterns)- Key focus: surface the week's recurring themes; skip gracefully on error

Frequently asked questions