Documentation
Documentation
16 skills in Documentation.
16 skills in this category.
Custom Time Entry Writer
Pick a recap template or saved prompt and output language, summarize the thread scoped to the active timer window since the last entry, preview it, then log on confirm — including catching up multiple retroactive entries. Runs manually on demand.
Deep Recap
Build a comprehensive ticket recap beyond the default template — full message/note/time-entry history, related sibling tickets for the client, a timeline, and current blockers. The "give me a REAL recap, not the two-line summary" workflow.
Doc Gap Detector
Find tickets where a security- or configuration-impacting change (firewall, MFA, DNS, admin access) was made with no linked or matching documentation update.
Environment Facts Updater
When a ticket reveals a client environment fact changed — new server, ISP, VPN, key contact — draft the corresponding documentation update for the client's doc platform.
KB Article Draft
Turn a resolved ticket into a reusable knowledge-base article draft — title, symptoms, cause, numbered resolution, and a "when this applies" section — with all client specifics stripped.
Knowledge Base Taxonomy
Design the category and tag structure for a knowledge base so articles are findable — a coherent hierarchy, a controlled tag vocabulary, and naming/placement rules — grounded in what the desk actually documents rather than an idealized tree.
Note Format Standard
Base skill defining the house format for internal ticket notes — structure, tone, and the plain-text rules for notes that sync to a PSA. Other skills reference this standard.
Post-Mortem & RCA Author
Write a structured post-mortem or root-cause analysis from an incident ticket — executive summary, event timeline, impact, root cause, and action items.
Runbook Recommender
Match a ticket against the desk's approved runbooks and post up to three runbook links as a single internal note — only when the fit is confident; otherwise post nothing.
SOP Builder
Write a full standard operating procedure — scope, prerequisites, numbered procedure, validation, and escalation criteria — from a ticket, an existing rough doc, or a described process.
SOP Candidate Finder
Sweep recently resolved tickets for documentation-worthy resolutions — recurring fixes, senior-only knowledge, vendor workarounds — and rank what should become an SOP or KB article.
Stale Doc Hygiene
Find documentation untouched for 180+ days, test it against current ticket reality, and produce a verification task list of docs to confirm, update, or retire.
Ticket Export for LLM
Produce a clean, sanitized, self-contained export of a ticket for pasting into another AI tool — credentials and PII stripped, context preserved.
Ticket Intake & Formatting
Build a clean ticket title and description from a raw report, voicemail, email, form submission, or rough technician notes, following the house intake standard.
Ticket Summary & Closure Note
Produce a clean summary of what happened on a ticket — resolution note, closure note, or a templated P1/P2 handoff summary — in the requested format and point of view.
Time Entry Cleanup
Turn raw, rough time notes into clean, standardized time entries — client-facing and internal versions — recording only work the engineer explicitly stated was done.
Related topics
Workaround DocumentationLiongard Network Documentation SyncConnect IT Glue Documentation to Ask MagicWas this page helpful?
⌘I