Example draft
Asking about ticket quality
Fictional example data; the complete input is included in the package.
Output excerpt
Fictional example data.
Did resolution time or reopen rate move along with first response? When we added automatic ticket tagging in March, our first-response time dropped, but reopens went from 8% to 11% over the next two months because some tickets landed in the wrong queue.
An excerpt from an Agent run using fictional data. Localized text does not imply a separate run. See references/example.md in the package for the full input, output and limits. This example is retained from v0.2.0; the added capability paths are optional and are not demonstrated by this example.
Input and output
You provide
Post URL/text, your contribution facts and the exact comment link when replying within a thread.
You get
Grounded comment options and a support map, checked against retrieved replies to avoid repeating an existing answer.
How to use
Supplied material works without API calls. Live data uses your SandBase connection and current API pricing; eligible calls share the daily free quota.
Download and unpack the complete Skill folder, keep its references, and use it with a local Agent that supports Skills.
Download Skill v0.3.0
Ask your Agent
Use linkedin-comment-drafter with my supplied material and scope. Use live lookups only when relevant to the task and within my budget. Deliver: Grounded comment options and a support map, checked against retrieved replies to avoid repeating an existing answer.