Claude Skills by OKHP3

Writes unit tests for code that already exists — choosing what deserves a test, what the cases are, and how to assert without welding the test to the implementation. Use this whenever the user asks for tests, unit tests, more coverage, or tests for a specific function or module, and also when adding to untested code where a characterization test is needed first. For building new code test-first, use test-driven-development.

Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.

Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.

OverKill Hill P³ ChatGPT project migration. Use when migrating, preserving, extracting, inventorying, normalizing, reconciling, or incorporating ChatGPT project threads, conversation exports, or complete chat histories into a repository. Also activate when a user needs a lossless thread archive, project-to-export crosswalk, provenance ledger, or public-safe distillation workflow. This is the authoritative capture and reconciliation process for ChatGPT project material in this repo -- use it e...

Create a durable continuation record when work pauses, becomes blocked, crosses a machine, or crosses an agent host. Use after substantial work or when the owner asks for a handoff. Record changed files, reasoning, evidence tiers, validation, limitations, and the exact next action without relying on chat memory.

Extract manually supplied xAI Grok conversations into standalone, actionable Markdown. Use when the user pastes a Grok chat, X-grounded answer, DeepSearch or reasoning output, prompt-response sequence, source list, connector result, image, video, file, or Canvas reference and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. Use...

Extract pasted or uploaded AI chat threads into standalone, actionable Markdown. Use when the user wants to evacuate context from ChatGPT, Claude, Gemini, Perplexity, Microsoft Copilot, Grok, Mistral Vibe, an unknown AI platform, or a mixed transcript; preserve goals, decisions, reasoning, next actions, prompts, code, files, images, citations, canvases, artifacts, diagrams, and provenance; resolve uncertain speaker boundaries; or requests rapid, balanced, comprehensive, essential, substantial...

Extract manually supplied ChatGPT conversations into standalone, actionable Markdown. Use when the user pastes a ChatGPT chat, Project thread, Canvas, Deep Research report, search answer, prompt-response sequence, generated file or image reference, or export excerpt and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. Use for c...

Extract manually supplied Claude conversations into standalone, actionable Markdown. Use when the user pastes a Claude chat, Project excerpt, Artifact, Research or web-search output, prompt-response sequence, uploaded-file reference, or export excerpt and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. Use for control-all copi...

Extract manually supplied Microsoft Copilot and Microsoft 365 Copilot chats into standalone, actionable Markdown. Use when the user pastes a Copilot chat, Work or Web-grounded answer, Copilot Page, agent output, prompt-response sequence, or references to files, emails, meetings, people, or tenant sources and wants goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, d...

Extract manually supplied Google Gemini conversations into standalone, actionable Markdown. Use when the user pastes a Gemini chat, Gem output, Canvas, Deep Research report, Workspace-grounded answer, file analysis, prompt-response sequence, image or audio reference, or export excerpt and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catal...

Extract manually supplied Mistral Vibe or former Le Chat conversations into standalone, actionable Markdown. Use when the user pastes a Vibe Work, Chat, or Code thread, Canvas, plan, tool trace, approval request, connector result, file analysis, prompt-response sequence, or export excerpt and wants its goals, reasoning, decisions, reusable assets, next actions, provenance, and missing sidecars preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or c...

Extract manually supplied Perplexity conversations into standalone, actionable Markdown. Use when the user pastes a Perplexity Thread, Space excerpt, Research or Create output, source-rich answer, prompt-response sequence, uploaded-file reference, or export excerpt and wants its goals, reasoning, decisions, citations, reusable assets, next actions, provenance, and missing sources preserved at rapid, balanced, comprehensive, essential, substantial, exhaustive, scan, distill, or catalog depth. ...

Design, author, evaluate, and package a reusable Microsoft Copilot Studio agent skill. Use when a task-specific capability must be created or shared across Copilot Studio agents powered by the GitHub Copilot harness. Do not use for Cowork packages, SharePoint site skills, GitHub repository skills, agent identity, knowledge-source design, or tool/connector implementation alone.

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.

Draft a durable decision record from an agreed discussion or source set. Use when capturing a decision, rationale, alternatives, trade-offs, owners, and follow-ups. Do not declare a decision made, update a register, or communicate it 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.

Turn an agreed meeting record into a reviewable decision and action closeout. Use when capturing decisions, owners, due dates, open questions, and follow-up drafts after a meeting. Do not send, post, create tasks, or modify calendars 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 current, source-linked project context pack from selected Microsoft 365 material. Use when preparing a project brief, handoff, onboarding packet, or status orientation. Do not search an unbounded tenant, share material, or alter files without explicit approval.

Build a source-linked research evidence log with confirmed, inferred, and unknown claims. Use when preparing a research brief, comparison, or decision memo from agreed sources. Do not treat search snippets as proof, publish a conclusion, or access sources outside the agreed boundary without approval.

Design, author, evaluate, and package a task-focused Microsoft Copilot Cowork skill. Use when converting a recurring personal Microsoft 365 workflow into a Cowork SKILL.md or M365 app-package skill. Do not use for SharePoint site skills, Copilot Studio agent skills, GitHub Copilot repository skills, or connector development alone.

Draft a source-grounded stakeholder update for review from an agreed project, time window, and audience. Use when summarizing status, decisions, risks, milestones, or asks for stakeholders. Do not send, post, share, or represent unverified information as fact 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.

Design, author, evaluate, and install-plan a task-focused GitHub Copilot Agent Skill. Use when creating a repository or personal GitHub Copilot SKILL.md for coding, review, maintenance, or repository workflows. Do not use for Cowork, SharePoint, Copilot Studio, or general agent instructions.

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.

Find likely canonical SharePoint library documents among selected related files and report stale or duplicate candidates with evidence. Use when users encounter conflicting final versions. Do not use to delete, archive, or declare a definitive source without owner review.

Extract specified obligation, renewal, notice, owner, counterparty, and risk fields from selected SharePoint contract files into a review queue. Use when contracts need operational visibility. Do not use to interpret legal obligations, update records, or send notices automatically.

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.

Prepare a reviewable handover inventory from selected SharePoint library files, with coverage gaps, ownership questions, and a proposed package manifest. Use when project documents need a controlled handover draft before copies, folders, permissions, or links are created or changed.

Classify selected SharePoint library files against an approved taxonomy and return confidence, exceptions, and a reviewable metadata draft. Use when new files need consistent filing guidance. Do not use to invent categories or silently move files.

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.

Answer a policy question from accessible SharePoint library documents with traceable citations, conflicts, and uncertainty. Use when a user needs a source-grounded policy summary from a named library or selected documents. Do not use for legal advice, invented policy, or uncited conclusions.

Review a SharePoint library for unpublished, stale, or checked-out files and return a remediation report with evidence. Use when visitors cannot reliably find usable content. Do not use to publish, check in, discard, or alter files automatically.

Review selected SharePoint library files against supplied records-readiness criteria and return a source-linked human review queue. Use when retention or record treatment needs a visible decision point. Do not use to apply labels or make retention decisions automatically.

Compare a SharePoint library's accessible tags, folders, and views with a supplied information architecture and report drift. Use when ad hoc uploads make a library harder to navigate. Do not use to rename, move, or retag files automatically.

Review a SharePoint List for missing required values, duplicate candidates, invalid controlled values, and inconsistent records. Use when a list owner needs a prioritized exception report and cleanup proposal. Do not use to silently repair, merge, delete, or rewrite list items.

Turn supplied decisions, approvals, and notes into reviewable SharePoint List decision records with source links and unresolved questions. Use when a decision log needs consistent draft entries before any List item is created or updated. Do not use to infer approval, authority, or an effective date.

Identify and explain likely duplicate SharePoint List records using supplied matching rules. Use when a list owner needs a review queue of duplicate candidates without merging, deleting, or overwriting records. Do not use to treat similar titles as confirmed duplicates.

Normalize SharePoint List intake items into a reviewable, schema-aligned draft. Use when new list items need required-field checks, controlled-value mapping, duplicate flags, or consistent descriptions before they are saved. Do not use to invent missing facts or silently update list items.

Turn unresolved questions and missing-content signals into a reviewable SharePoint List knowledge-gap draft. Use when a site team needs a visible, owned backlog of questions, impact, and proposed source research. Do not use to invent answers, perform external research, or create List items silently.

Turn supplied meeting notes into a reviewable SharePoint List action draft. Use when decisions, owners, due dates, and follow-up actions need consistent fields and duplicate checks before list items are created or updated. Do not use to infer commitments, assign people, or write action records without confirmation.

Create a cited portfolio-health brief from supplied SharePoint List fields and owner-approved health rules. Use when project, initiative, or work-item signals need a consistent executive exception summary. Do not use to invent portfolio status, alter items, or make funding or delivery decisions.

Triage SharePoint List requests into a transparent review queue using supplied routing rules. Use when request items need completeness checks, category suggestions, priority flags, or owner-ready next steps. Do not use to assign people, change status, or route requests without explicit rules and confirmation.