
Claude Skills by OKHP3
github.com/OKHP3Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
Rebuild and validate Skillz Forge catalog truth, evidence contracts, and provenance without credentials.
Validate a project change, draft, research packet, skill, promotion package, or handoff before it is treated as complete. Use after meaningful work and before handoff, graduation, publication review, or reliance on an artifact. Run the identified project validator when one exists, then add judgment checks the script cannot prove.
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 pr...
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 capturin...
Preserve one raw idea, file, link, transcript, or request in a project inbox with provenance and minimal handling. Use when material first arrives and must be captured before interpretation, grouping, scoping, or promotion. Do not use for batch triage or lifecycle decisions.
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...
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.
Assess an incomplete or newly proposed Custom GPT concept for build readiness. Use when a user has a GPT idea, partial notes, pasted conversation, draft instructions, knowledge files, or an unfinished GPT and needs an evidence inventory, explicit gaps, targeted elicitation, a readiness score, or a structured handoff to okhp3-custom-gpt-builder.
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...
Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill when you need to gather process knowledge from subject matter experts; when the user wants a question plan before an interview or workshop; when elicitation is incomplete and gaps need targeted follow-up; when they say "help me interview the process owner", "prepare questions for the workshop", or "what should I ask to fill in the missing steps". Produces a question plan and el...
Evaluate a document, report, spreadsheet, hypothesis, decision memo, or Agent Skill with independent evidence review, conditional disruption, and evidence-based adjudication. Use when testing whether an artifact is trustworthy, sufficiently supported, safe to act on, or ready to release. Also activate for multi-agent review design, falsification passes, claim ledgers, or structured quality gates. Do not use as a substitute for a domain-specific statistical, legal, medical, or security review.
Classify consequential claims as confirmed, inferred, proposal, or unknown and keep those tiers visible. Use for cross-machine or cross-agent comparisons, conflicting sources, handoffs, decision records, and recommendations from incomplete evidence. Do not substitute it for mechanical validation or source research.
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 fir...
Plan conversion of an existing Custom GPT into a portable Agent Skill. Use when a GPT already has instructions, knowledge files, actions, conversation starters, test prompts, or usage history and the user needs a capability map, semantic-loss analysis, reusable skill boundary, migration plan, or handoff to okhp3-skill-foundry.
Decide whether an active exploratory effort is ready to become formal, should remain active, should archive, or is blocked. Use when an effort feels ready, the owner asks for a go or no-go, or a promotion package needs a readiness decision. Score evidence rather than enthusiasm and do not create the destination.
Assemble all validated BP-SKILL process artifacts into a publication-ready bundle with a manifest, approvals record, and completeness check. Use this skill when the user is ready to publish or hand off a complete process documentation set; when they ask to package the process docs, create a handoff bundle, publish the process artifacts, or generate a release package. Requires a passing validation report (Band A or B) before bundling. Produces a MANIFEST.yaml, APPROVALS.yaml, and a ZIP-ready d...
Use this skill whenever an agent needs to export, capture, ingest, summarize, route, deduplicate, or reconcile a conversation or content artifact into Notion. It guides connector-enabled agents through choosing a Notion page versus database destination, resolving a workspace-specific URL or ID, inspecting page content or data-source schema before writing, mapping thread metadata and reusable extracts, creating or updating records safely, and verifying the result. Trigger for ChatGPT, Claude, ...
Design and operationalize outcome models that compress noisy event histories into calibrated forecasts and constrained decisions. Use when a user asks about feature reduction, probability, expected value, aggregation, or moving a prediction method between sports, business, sales, advertising, finance, or prediction markets. Load a domain adapter when one fits.
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.
Capture a recurring task as either a backlog entry or a new skill skeleton. Use when the user says "I keep doing X", "this is the third time", "make this a skill", "let's capture this", or at the natural end of a work session when a repeatable pattern just occurred. Extracts the pattern from conversation context (tools used, sequence of steps, input/output formats, corrections made) and produces either a BACKLOG.md line or a SKILL.md skeleton following this repo's conventions — not full skill...
Identify deviations, gaps, and exception paths between an as-is process capture and its intended design. Use this skill when the user wants to find where a process breaks down, where steps are missing or inconsistent, where exception handling is undefined, or where current execution differs from documented procedure. Use when they say "what's wrong with the current process", "find the gaps", "where does this break", or "analyze exceptions". Produces a gap analysis report and exception catalog.
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 Reco...
Prepare an exploratory effort that cleared the graduation gate for owner-approved formalization. Use to assemble the destination brief, provenance, decisions, risks, artifact inventory, and first formal-project action. Do not create repositories, publish, push, or move work externally without separate authorization.
Clean up a single Replit-hosted Git repository — squash-merge and delete old, merged, or abandoned branches and pull requests (including Replit-generated subrepl-*, replit-agent, and agent/* branches), and normalize file/folder names against a kebab-case default with documented exceptions. Use when a user asks to purge dead/stale branches, clean up merged PRs, decrapify or tidy the repo, fix inconsistent file naming, or wants a repeatable Replit-repo hygiene routine across multiple Repls.
Reconcile a collection of local Git repositories with their GitHub origins, inspect all local variations against origin/main, preserve uncommitted or unreachable work, and manage branch lifecycle. Use when a user has multiple clones or computers, needs to find differences from origin/main, recover forgotten work, review agent/Copilot/Dependabot branches, merge completed pull requests, prune verified redundant branches, or establish a repeatable daily or weekly repository-maintenance routine.
OverKill Hill P³ repository organizer for content-first Git repositories. Use when a local Git repository grew organically from a folder and needs an evidence-based profile, purpose summary, classification, cross-platform naming cleanup, folder design, governance scaffolding, or a safe reorganization plan. Also activate when a repository contains prompts, AI conversations, research, Word documents, spreadsheets, PDFs, images, or mixed knowledge assets rather than a conventional application. T...
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.
OverKill Hill P³ skill cataloger. Inventory and validate repository-local Agent Skills, then safely regenerate a marked README catalog and machine-readable catalog metadata. Use when asked to list, audit, version-check, validate, or refresh skills under .agents/skills/, or to index a distribution repository’s root family folders. Choose catalog mode for a project surface and explicit --full mode for a distribution index; use --check or --dry-run when no file changes are authorized.
Find, verify, compare, and route to project-local, installed, runtime, or plugin-provided agent skills. Use when the user asks what skills exist, how to invoke one, or when the correct reusable workflow is unclear. Do not use it to install unavailable capabilities without an explicit request.
Create, audit, test, and improve portable Agent Skills with evidence-backed instructions, progressive disclosure, risk-based evaluations, and release checks. Use when authoring a new SKILL.md, improving an existing skill, designing or grading evaluations, diagnosing weak trigger behavior, or synchronizing a skill across repositories. Also activate when a workflow should become a reusable skill or a skill must improve itself without making unsupported quality claims. This is the authoritative ...
Promote and synchronize a project-local Agent Skill into a portable, reviewable distribution package. Use when a skill under .agents/skills needs a publication mirror, provenance record, canonical family assignment, or a safe handoff into OKHP3/skillz. Also activate when multiple SKILL.md copies must be compared or reconciled. Do not use for generic repository publishing.
Produce research notes, comparisons, or recommendations with traceable sources, retrieval dates, and explicit uncertainty. Use when work depends on external facts, changing information, technical documentation, or claims that should be verified. Do not use when the needed evidence is already fully available in local files.
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...
Review one or more project inbox items and assign a recorded lifecycle disposition. Use for inbox sweeps, duplicate resolution, grouping related captures, activating an effort, identifying a graduation candidate, archiving, or requesting owner input. Do not publish or move work outside the project.
OverKill Hill P³ Vite-to-GitHub-Pages deployment runbook. Use when deploying or troubleshooting this React/Vite app, its Actions workflow, /abrahamic-reference-engine/ production base, BrowserRouter basename fallback, dist artifacts, build validation, or Pages environment variables. Also activate for subpath asset failures or SPA refresh diagnosis. Do not use for gh-pages branches, backend hosting, or unrelated UI work.
Build the standalone Forge artifact with strict routing inputs and confirm its static output exists.
Confirm the live Skillz Forge GitHub Pages site matches the last successful deploy run, independent of whether the last deploy-pages.yml run happened to report success.
Confirm the published Skillz Forge review surface still preserves failed-contract keyboard recovery after a GitHub Pages deploy.
Verify GitHub Pages publishing remains family-agnostic and fail-closed.
Check Forge route declarations and hash-anchor targets without requiring a browser dependency.
Exercise validator failure boundaries with dependency-free malformed, missing-output, route, and publishing fixtures.
Compare shared themes across Judaism, Christianity, and Islam using 20 seeded passage sets, neutral bridging notes, and the ARE proportional-representation rule. Use for side-by-side scripture comparisons, interfaith education, neutral common-ground explanations, comparison UI work, or requests about what these traditions share. Do not use it to rank traditions, prove theological priority, or invent a parallel where none is established.
Fetch, compute, and format religious observance calendars for the three in-scope Abrahamic traditions of the Abrahamic Reference Engine: Judaism, Christianity, and Islam. Use this skill whenever an agent needs to retrieve religious holiday data, generate iCalendar (.ics) output, look up holiday descriptions for cross-tradition audiences, or produce a unified observance event list. Covers Hebcal API (Jewish), AlAdhan API (Islamic), TypeScript Computus algorithm (Christian -- Western and Orthod...
Reference ARE scope, canon, denominations, translations, Pew US shares, and free API providers for Judaism, Christianity, and Islam. Use before answering canon or denomination questions, choosing a translation, writing scripture fetch code, checking whether a tradition is in scope, or explaining LDS, Catholic, Orthodox, Jewish, or Islamic reference coverage. Preserve denominational variation, source dates, licensing, and known API gaps.
Fetch or integrate scripture passages from Judaism, Christianity, or Islam through the ARE free anonymous providers. Use for verse lookup, API endpoint and reference-format questions, translation IDs, normalization, attribution, error handling, fallback routing, or denomination-aware scripture UI work. Covers Sefaria, bible-api.com, Quran.com with AlQuran.cloud fallback, and LDS Standard Works routing. Never invent text or silently change translations.
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.
Assess an incomplete or newly proposed Custom GPT concept for build readiness. Use when a user has a GPT idea, partial notes, pasted conversation, draft instructions, knowledge files, or an unfinished GPT and needs an evidence inventory, explicit gaps, targeted elicitation, a readiness score, or a structured handoff to okhp3-custom-gpt-builder.