Documents & office

Third-party API integrations with Planner/Builder/Tester loop. Use for /oc-integrate, "connect to Salesforce", "webhook", "OAuth", "API integration", "connect to Slack", or any external service connection. For designing or building your *own* first-party API (OpenAPI/GraphQL authoring, versioning, SDK generation), use oc-api-dev instead. When the destination is the data warehouse, this skill builds the connector; the warehouse-bound pipeline + data contract side is oc-data-ops.

Third-party API integrations with Planner/Builder/Tester loop. Use for /oc-integrate, "connect to Salesforce", "webhook", "OAuth", "API integration", "connect to Slack", or any external service connection. For designing or building your *own* first-party API (OpenAPI/GraphQL authoring, versioning, SDK generation), use oc-api-dev instead. When the destination is the data warehouse, this skill builds the connector; the warehouse-bound pipeline + data contract side is oc-data-ops.

Reverse-engineer existing code into spec docs. Use for /oc-rev-spec, /oc-reverse-spec, /oc-rev-full, /oc-rev-scan, /oc-rev-design, /oc-rev-stack, /oc-rev-sprint, "document this codebase", "generate specs from code", "backfill specs", or when pointing at existing code that needs documentation.

Reverse-engineer existing code into spec docs. Use for /oc-rev-spec, /oc-reverse-spec, /oc-rev-full, /oc-rev-scan, /oc-rev-design, /oc-rev-stack, /oc-rev-sprint, "document this codebase", "generate specs from code", "backfill specs", or when pointing at existing code that needs documentation.

Reverse-engineer existing code into spec docs. Use for /oc-rev-spec, /oc-reverse-spec, /oc-rev-full, /oc-rev-scan, /oc-rev-design, /oc-rev-stack, /oc-rev-sprint, "document this codebase", "generate specs from code", "backfill specs", or when pointing at existing code that needs documentation.

Reverse-engineer existing code into spec docs. Use for /oc-rev-spec, /oc-reverse-spec, /oc-rev-full, /oc-rev-scan, /oc-rev-design, /oc-rev-stack, /oc-rev-sprint, "document this codebase", "generate specs from code", "backfill specs", or when pointing at existing code that needs documentation.

Founder advice after six YC-style questions. Use whenever a founder is stuck or unsure what to ask, or /c-level-agents:office-hours.

Full-text search inside Word, PPT, Excel and PDF files, with precise locators.

Read your officina.it workshop data: customers, vehicles, worksheets, invoices, calendar.

Reconcile open follow-ups or refresh an activity log from Sent Items, inbox, calendar, and supplied evidence. Use when checking which replies were already sent, which evidence gaps can be resolved, or what changed through a cutoff. Excludes drafting, sending, and deciding overall application status.

Capture and normalise a current-state process description into a structured as-is process YAML with stable step identifiers. Use this skill when the user has a process that is already running and needs to document its current state before gap analysis or redesign; when they provide step lists, SOPs, or process notes that need to be structured; when they say \"document what we do today\", \"capture the current process\", or \"baseline the process before we change it\". Do not use this skill to design a target state or propose changes — that is okhp3-future-state-change-strategy; this skill records only what happens today. Produces a structured as-is process artifact with normalised step IDs.

Capture and normalise a current-state process description into a structured as-is process YAML with stable step identifiers. Use this skill when the user has a process that is already running and needs to document its current state before gap analysis or redesign; when they provide step lists, SOPs, or process notes that need to be structured; when they say "document what we do today", "capture the current process", or "baseline the process before we change it". Produces a structured as-is process artifact with normalised step IDs.

OverKill Hill P³ AskJamie SPA styling. Use when a user wants an AskJamie application, documentation artifact, presentation, or image brief aligned to the approved AskJamie profile. Also activate when a target needs calm, mid-century helpdesk clarity for complex decisions. This specialization applies the approved local profile and does not substitute OverKill Hill or Glee-fully styling.

Draft an email or direct message the owner will send as themselves, using the AskJamie lens method (Represent, Frame, Investigate, Protect). Reads the full thread, flags every commitment and unknown, runs a tone and over-promising check, and returns a draft plus notes. Use when asked to draft, reply to, or rewrite correspondence. Never sends.

OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand, visual style, palette, typography system, layout language, or interface aura from a website, stylesheet, document, presentation, infographic, or set of visual assets. Also activate when a user wants an SPA, documentation, presentation, image brief, or other target artifact aligned to one or more named style profiles. This is the authoritative profile-driven workflow for capturing and applying visual style without blending unrelated brands or treating inferred cues as declared rules.

OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand, visual style, palette, typography system, layout language, or interface aura from a website, stylesheet, document, presentation, infographic, or set of visual assets. Also activate when a user wants an SPA, documentation, presentation, image brief, or other target artifact aligned to one or more named style profiles. This is the authoritative profile-driven workflow for capturing and applying visual style without blending unrelated brands or treating inferred cues as declared rules.

OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand, visual style, palette, typography system, layout language, or interface aura from a website, stylesheet, document, presentation, infographic, or set of visual assets. Also activate when a user wants an SPA, documentation, presentation, image brief, or other target artifact aligned to one or more named style profiles. This is the authoritative profile-driven workflow for capturing and applying visual style without blending unrelated brands or treating inferred cues as declared rules.

OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand, visual style, palette, typography system, layout language, or interface aura from a website, stylesheet, document, presentation, infographic, or set of visual assets. Also activate when a user wants an SPA, documentation, presentation, image brief, or other target artifact aligned to one or more named style profiles. This is the authoritative profile-driven workflow for capturing and applying visual style without blending unrelated brands or treating inferred cues as declared rules.

Find and reconcile the user's commitments across an agreed set of email and meeting sources. Use when preparing an accountable follow-up list, checking promises, or identifying open commitments. Do not assign commitments, send reminders, create tasks, or alter records without explicit approval.

Build a realistic personal execution brief from an agreed day's priorities, calendar, and commitments. Use when planning today, resolving calendar conflicts, or choosing the next action. Do not schedule, send, delegate, or alter tasks or calendar items without explicit approval.

Critique a draft against an explicit audience, purpose, quality bar, and risk checklist. Use when reviewing a document, presentation, memo, or proposal for clarity, structure, evidence, and safe communication. Do not rewrite, send, share, or approve the document without explicit direction.

Propose a safe folder, naming, and retention cleanup plan for selected files. Use when reviewing document sprawl, duplicate candidates, folder structure, or records-retention questions before any file moves. Do not move, rename, delete, share, or change retention labels without explicit approval.

Triage a Microsoft 365 inbox into a prioritized, reviewable work queue. Use when organizing email, identifying follow-ups, preparing reply drafts, or separating urgent messages from newsletters and FYI. Do not use to send, delete, archive, unsubscribe, or create rules without explicit approval.

Prepare a concise meeting brief from an agreed calendar event and relevant Microsoft 365 context. Use when gathering agenda, attendees, open decisions, and pre-read material for a meeting. Do not schedule, update, invite, message, or send material without explicit approval.

Create a personal weekly review from an agreed Microsoft 365 work window. Use when summarizing commitments, completed work, open loops, calendar load, and priorities for next week. Do not schedule, send, delegate, delete, or modify tasks or files without explicit approval.

Build, audit, and improve OpenAI Custom GPTs with production-grade methodology. Use this skill when the user asks to create, configure, test, evaluate, audit, improve, troubleshoot, compare, document, or package a Custom GPT or reusable ChatGPT workflow. Also use it for GPT Builder instructions, knowledge files, Actions, Apps/connectors, GPT Store readiness, Gemini Gem comparison, Copilot declarative-agent comparison, or conversion between Custom GPTs and Agent Skills.

Build, audit, and improve OpenAI Custom GPTs with production-grade methodology. Use this skill when the user asks to create, configure, test, evaluate, audit, improve, troubleshoot, compare, document, or package a Custom GPT or reusable ChatGPT workflow. Also use it for GPT Builder instructions, knowledge files, Actions, Apps/connectors, GPT Store readiness, Gemini Gem comparison, Copilot declarative-agent comparison, or conversion between Custom GPTs and Agent Skills.

Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS contains three or more gateway decision points that warrant a structured decision table; when the user asks to document business rules as decision logic, build a DMN table, or make decision criteria explicit. This is a recommended extension skill triggered automatically when okhp3-visual-process-modeling identifies three or more gateways. Do not use it for fewer than three decision points — document those inline in the PNS decision_points section instead. Produces a decision-model YAML and a human-readable DMN rule table.

Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS contains three or more gateway decision points that warrant a structured decision table; when the user asks to document business rules as decision logic, build a DMN table, or make decision criteria explicit. This is a recommended extension skill triggered automatically when visual-process-modeling identifies three or more gateways. Produces a decision-model YAML and a human-readable DMN rule table.

Review a document, report, spreadsheet, hypothesis, decision memo, or Agent Skill with independent evidence review, conditional disruption, and bounded adjudication. Use for claim ledgers, falsification passes, and release gates. Do not replace required statistical, legal, medical, financial, or security authority.

Review a document, report, spreadsheet, hypothesis, decision memo, or Agent Skill with independent evidence review, conditional disruption, and bounded adjudication. Use for claim ledgers, falsification passes, and release gates. Do not replace required statistical, legal, medical, financial, or security authority.

Design a target-state process and a structured change strategy from a gap analysis. Use this skill when the user wants to redesign a process after gaps have been identified; when they ask \"what should the process look like\", \"how do we fix this\", \"design the to-be process\", or \"build a change plan\". This is a recommended extension skill — use after okhp3-process-gap-exception-analysis has produced a gap analysis. Do not use it to document only the current state — that is okhp3-as-is-process-capture; this skill designs what should change, not what exists today. Scope firewall applies: never include employer-proprietary constraints without explicit user authorisation. Produces a future-state process artifact and a change strategy document.

Design a target-state process and a structured change strategy from a gap analysis. Use this skill when the user wants to redesign a process after gaps have been identified; when they ask "what should the process look like", "how do we fix this", "design the to-be process", or "build a change plan". Produces a future-state process artifact and a change strategy document. This is a recommended extension skill — use after process-gap-and-exception-analysis has produced a gap analysis. Scope firewall applies: never include employer-proprietary constraints without explicit user authorisation.

OverKill Hill P³ Glee-fully SPA styling. Use when a user wants a Glee-fully application, documentation artifact, presentation, or image brief aligned to the approved Glee-fully profile. Also activate when a target needs retro-bright, warm, emotionally intelligent tooling. This specialization applies the approved local profile and does not substitute OverKill Hill or AskJamie styling.

OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand, visual style, palette, typography system, layout language, or interface aura from a website, stylesheet, document, presentation, infographic, or set of visual assets. Also activate when a user wants an SPA, documentation, presentation, image brief, or other target artifact aligned to one or more named style profiles. This is the authoritative profile-driven workflow for capturing and applying visual style without blending unrelated brands or treating inferred cues as declared rules.

Run a WWGD (What Would Glee Do, Say, Think, Feel) reception check on a draft email, post, article, or message using the Glee-fully persona lens. Scores warmth, kindness, clarity, joy, and "does this sound like the author or like a jerk", then returns keep-or-soften notes. Use when asked for a WWGD check, a warmth pass, or "how will this land". Not a proxy for any real person's opinion.

OverKill Hill P³ OverKill Hill SPA styling. Use when a user wants an OverKill Hill application, documentation artifact, presentation, or image brief aligned to the approved OverKill Hill profile. Also activate when a target needs the forge-like technical visual system of the OverKill Hill family. This specialization applies the approved local profile and does not substitute Glee-fully or AskJamie styling.

OverKill Hill P³ OverKill Hill SPA styling. Use when a user wants an OverKill Hill application, documentation artifact, presentation, or image brief aligned to the approved OverKill Hill profile. Also activate when a target needs the forge-like technical visual system of the OverKill Hill family. This specialization applies the approved local profile and does not substitute Glee-fully or AskJamie styling.

Conduct structured process intake and scope definition using BABOK v3 elicitation techniques. Use this skill when the user wants to document a business process from scratch; when they describe a workflow, procedure, or set of steps and need it structured; when they ask to scope a process, define process boundaries, or capture business rules; when they say "help me document this process", "let's scope out this workflow", or "what are the inputs and outputs"; when you need a Process Intake Record (PIR) as input for downstream narrative, modeling, or SOP skills.

Conduct structured process intake and scope definition using BABOK v3 elicitation techniques. Use this skill when the user wants to document a business process from scratch; when they describe a workflow, procedure, or set of steps and need it structured; when they ask to scope a process, define process boundaries, or capture business rules; when they say \"help me document this process\", \"let's scope out this workflow\", or \"what are the inputs and outputs\"; when you need a Process Intake Record (PIR) as input for downstream narrative, modeling, or SOP skills. This is the first-pass discovery skill; once a PIR exists, use okhp3-elicitation-interviews to fill remaining gaps rather than restarting intake.

Author and validate a Process Narrative Specification (PNS) from a PIR and stakeholder register. Use this skill when you have a completed Process Intake Record from okhp3-process-intake-and-scope and need to produce a structured narrative document that anchors ISO 9001 §4.4.1 process-box semantics, BABOK Core Concept Model, RACI matrix, SIPOC table, business rules, decision points, KPIs, and controls. Do not use it when only a quick diagram is needed without governance structure — go directly to okhp3-visual-process-modeling for that. The PNS is the authoritative handoff input for okhp3-visual-process-modeling, okhp3-sop-work-instructions, okhp3-raci-governance-matrix, and okhp3-sipoc-generation.

Model vendor, customer, purchase-order, invoice, quotation, document, status, notification, and partner-specific transaction flows in an EDI-like portal. Do not assume formal EDI compliance without evidence.

Plan and build a structured multi-frame Replit canvas presentation board — hero rows, labeled zones, iframe lifecycle (building→live), coordinate layouts, and focusCanvasShapes for audience navigation. Use when organising the canvas for a designathon, showcase, or any multi-frame review. Also activate for "arrange the frames", "set up the board", "label the zones", "focus the viewport", or any canvas layout that needs deliberate spatial planning rather than ad-hoc placement.

Plan and build a structured multi-frame Replit canvas presentation board — hero rows, labeled zones, iframe lifecycle (building→live), coordinate layouts, and focusCanvasShapes for audience navigation. Use when organising the canvas for a designathon, showcase, or any multi-frame review. Also activate for "arrange the frames", "set up the board", "label the zones", "focus the viewport", or any canvas layout that needs deliberate spatial planning rather than ad-hoc placement.

Create reusable role-family master resumes from an existing career evidence library. Use for several broad career lanes or stable resume baselines in Markdown and DOCX. This is not corpus ingestion or tailoring to one opening.

Review selected SharePoint library documents for supplied accessibility and structure checks, then return an evidence-led remediation draft. Use when document visitors need more usable content. Do not use to certify accessibility or alter files automatically.

Curate selected SharePoint document-library articles into a reviewable collection with titles, summaries, categories, and duplicate signals. Use when a knowledge library needs consistent article recommendations before any file or metadata change. Do not use to publish, move, rename, or alter files silently.

Check selected SharePoint library documents against supplied minimum quality rules for naming, sections, dates, ownership, and template markers. Use when a library needs a reviewable publication-quality report. Do not use to certify or edit documents automatically.

Review SharePoint document-library metadata for completeness, controlled-value conformance, and inconsistent records. Use when a library owner needs a traceable exception report and proposed fixes before any metadata update. Do not use to silently edit files, fields, or library settings.

Draft a new Slack channel message for a supplied workspace destination. Use when the user needs a clear announcement, update, question, or handoff for a named Slack channel. It returns formatted draft text only and does not send, schedule, direct-message, mention broadly, attach files, react, or change workspace or channel settings.