Draft first replies to customers and identify tickets that require human review before sending. The skill defines sensitive cases to escalate and guides replies that explain the next action, name who handles it, and match the customer's tone.
When a ticket must go to a human before any reply is sent, and how the first reply should read. Use when drafting a customer reply or setting needs_human_review.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this skill when drafting the first reply to a customer, or when deciding whether a ticket needs a human before anything is sent.
Set needs_human_review to true, and do not send an automated reply, when the ticket involves any of:
Urgency alone is not escalation. A production outage with a known cause and a workaround is urgent and still does not need human review.
Open with what you understood, in the customer's own terms, before saying what you will do. Never open with an apology template.
Say what happens next and who does it. "I have routed this to our billing team, who will reply today" beats "your ticket has been escalated".
Do not promise a timeline the team has not committed to. If you do not know when something will be fixed, say what you will tell them and when.
Match the customer's register. A one-line question gets a one-line answer; a detailed report gets a reply that addresses each part in the order they raised it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add AI models to Kiln or find available models missing from its list. The skill checks provider model identifiers and capabilities, updates model settings, runs tests against real APIs, and drafts a Discord announcement.
Find documentation and agent instructions made outdated by a branch’s code changes. Update affected paths, commands, settings, and behavior descriptions in place, then commit the documentation fixes alongside the code in the same pull request.
Audit Kiln’s model list against provider APIs and catalogs to identify removed models and upcoming retirements. Get findings organized by provider, then mark affected entries as deprecated after reviewing and approving the proposed changes.
Check whether Kiln’s base models still support fine-tuning, the process of adapting a model with additional training. Compare configured identifiers and Fireworks’ allowlist with provider information, then report unsupported entries and recommend specific updates.
Apply Kiln’s coding rules when editing or reviewing Python, TypeScript, and Svelte. The skill combines area-specific guidance with a script that checks changed lines, plus manual checks for architecture, configuration handling, shared state, and asynchronous operations.
Maintain Kiln’s list of large language models by discovering new releases, testing provider access, and marking unavailable entries as deprecated. Prepare pull requests, report unresolved issues, and check whether the updated list needs publication.