Skills directory · page 46

Design a secure modernization target for a reclaimed web application, including architecture, data, identity, integrations, observability, and deployment decisions. Do not turn a proposal into implementation prematurely.

Produce evidence-led technical documentation for an undocumented application, including architecture, operations, code tours, data dictionaries, and security findings. Expose uncertainty instead of smoothing it over.

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.

Validate and hand off the reclaimed understanding, documentation, tests, risks, and next actions for continued support or replacement of an undocumented application. Distinguish passed, failed, blocked, and not-run evidence.

Reconcile misplaced record folders, file versions, and references across a local library, synced drive, or tracker. Use to audit filing locations, preserve versions during authorized moves, repair affected links, or verify local and cloud parity. Application status belongs to a separate workflow.

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 authoring (that's skill-creator's job once a skeleton exists).

Draft a Reddit comment or nested reply from supplied submission, thread, and community-rule context. Use when the user wants a grounded contribution to a named Reddit conversation. It returns a draft only and does not comment, vote, report, message moderators, moderate content, or coordinate engagement.

Draft a Reddit text, link, image, or media submission for a supplied community. Use when the user needs a community-aware Reddit post that respects supplied rules, post form, title requirements, and flair context. It prepares a draft only and does not submit, vote, join communities, message moderators, apply flair, or manipulate engagement.

Core ReFolDec transformation skill. Use when the task is explicitly about transforming an artifact from one representation type to another — folding an idea or process into a compact form, unfolding an artifact into its primitives, or refolding across representation types (diagram to documentation, documentation to SKILL.md, SKILL.md to procedure). Also use when semantic loss across a transformation needs to be tracked or compared. This is not a general writing or diagramming skill — it is a representation-change skill. Load domain skills (okhp3-mermaid-core, okhp3-recurring-task-capture) alongside this skill when the transformation target is a diagram or a skill skeleton.

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.

Full playbook for a Replit Designathon competition submission — canvas organisation for judges, artifact selection, dual deployment (Replit Publish + GitHub Pages), session-to-session narrative continuity, and building-in-public commit discipline. Activate for "designathon", "competition", "building in public", "judges", "showcase", "submission", "dual deploy", "GitHub Pages + Replit", or any request to prepare a Replit project for public or competitive review.

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.

Review and score fresh Replit BuildHub contest submissions with live rubric checks, safe public-app exploration, and verified per-project idempotency. Use when bulk-reviewing user-supplied Replit contest project URLs. Also activate when scoring availability or favorite state may differ between projects or change during a review batch. Do not use for virtual investments, contest manipulation, or unrelated Replit app changes.

The complete Replit design iteration loop as a single coherent workflow — extract → sandbox → variant → graduate. Use when redesigning, improving, or creating variants of any UI component or page. Covers the "extract first, never approximate" rule, DESIGN subagent brief anatomy, variant labelling conventions on canvas, and the graduation decision gate. Activate for "redesign", "improve this component", "show me options", "create variants", "put on canvas", "graduate this mockup", "design alternatives", or any request that implies iterating on UI — whether the component exists already or is being built from scratch.

Keep Replit project work autonomous and Free Mode-first with bounded execution, checkpointed quota recovery, and quiet upgrade handling. Use when the user asks to maximize Free Mode, avoid repeated upgrade nudges, retry after a five-hour or weekly limit, preserve work across interruptions, or keep routine work moving without unnecessary approval pauses. Does not bypass quotas or human approval.

Recover and maintain safe GitHub synchronization for a Replit project. Use when Replit reports PUSH_REJECTED, cannot commit through its UI, or a project needs to pull, commit, reconcile, merge, or push changes to its GitHub default branch. Also activate for "Replit GitHub out of sync", "push rejected", "sync Replit to origin/main", or a safe branch-to-main squash merge. Do not use to force-push, discard unreviewed work, or bypass branch protection.

Navigate and build in a Replit pnpm multi-artifact monorepo without silent failures. Covers the non-obvious rules that cause blank previews, port conflicts, workflow naming errors, and broken cross-artifact imports: BASE_URL prefix discipline, PORT env var reading, managed workflow naming, pnpm catalog drift, and workspace:* shared library wiring. Activate for "add an artifact", "create a new app", "preview path", "port conflict", "blank preview", "shared package", "workflow naming", "pnpm catalog", "cross-artifact", or any time a second artifact is being added to an existing Replit project.

OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout. Use when a user asks to clean up merged or abandoned branches and pull requests, purge stale subrepl-* or agent/* branches, normalize file and folder names, or remove repository detritus. Also activate for "decrapify this Repl", "tidy this repo", "prune dead branches", or "fix inconsistent filenames". This is the authoritative one-time cleanup workflow for one Replit checkout; use okhp3-repository-janitor for recurring maintenance and multiple local clones, and okhp3-repository-organizer for structural reorganization.

OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout. Use when a user asks to clean up merged or abandoned branches and pull requests, purge stale subrepl-* or agent/* branches, normalize file and folder names, or remove repository detritus. Also activate for "decrapify this Repl", "tidy this repo", "prune dead branches", or "fix inconsistent filenames". This is the authoritative one-time cleanup workflow for one Replit checkout; use okhp3-repository-janitor for recurring maintenance and multiple local clones, and okhp3-repository-organizer for structural reorganization.

OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout. Use when a user asks to clean up merged or abandoned branches and pull requests, purge stale subrepl-* or agent/* branches, normalize file and folder names, or remove repository detritus. Also activate for "decrapify this Repl", "tidy this repo", "prune dead branches", or "fix inconsistent filenames". This is the authoritative one-time cleanup workflow for one Replit checkout; use okhp3-repository-janitor for recurring maintenance and multiple local clones, and okhp3-repository-organizer for structural reorganization.

OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout. Use when a user asks to clean up merged or abandoned branches and pull requests, purge stale subrepl-* or agent/* branches, normalize file and folder names, or remove repository detritus. Also activate for "decrapify this Repl", "tidy this repo", "prune dead branches", or "fix inconsistent filenames". This is the authoritative one-time cleanup workflow for one Replit checkout; use okhp3-repository-janitor for recurring maintenance and multiple local clones, and okhp3-repository-organizer for structural reorganization.

OverKill Hill P³ one-Repl repository cleanup workflow for safely auditing and tidying a single Replit workspace's Git checkout. Use when a user asks to clean up merged or abandoned branches and pull requests, purge stale subrepl-* or agent/* branches, normalize file and folder names, or remove repository detritus. Also activate for "decrapify this Repl", "tidy this repo", "prune dead branches", or "fix inconsistent filenames". This is the authoritative one-time cleanup workflow for one Replit checkout; use okhp3-repository-janitor for recurring maintenance and multiple local clones, and okhp3-repository-organizer for structural reorganization.

Execute Replit-planned tasks with an external coding agent while Replit remains project manager and designer. Use for task handoff, architecture, implementation, and returning verified results for Replit acceptance. Supports a selected task or an explicitly bounded backlog. Does not dispatch coding to Replit, cancel cards by default, or invent board-completion APIs.

Create governed FoundRy child repositories from Custom GPTs, Gemini Gems, Copilot agents, prompt bundles, Notion concepts, research notes, or prototype ideas. Use whenever the user wants to migrate an AI capability into GitHub, standardize a repo, create a child repo scaffold, or convert platform-specific AI work into a reusable capability package.

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.

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. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.

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. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.

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. This is the authoritative workflow for understanding and organizing an existing repository; use it instead of application-template advice, skill cataloging, or new-repository creation workflows.

Audit and configure GitHub repository settings for one owner working with AI agents. Use for branch protection, merge options, Actions, Pages, environments, Copilot review, MCP configuration, or repeatable read-only drift audits, including post-scaffold FoundRy setup. Distinguish owner preferences from platform requirements and verify each write. Do not use for repository creation, code review itself, fleet cleanup, or deployment.

Revise or renew a sourced long-form research and retrieval knowledge file while preserving its original purpose, sources, and limitations. Use for topic-drift correction, cited document renewal, and source-to-revision comparison. It does not certify retrieval or publish automatically.

Compare defensive responses using expected loss, effectiveness, uncertainty, reversibility, and response cost. Use when triaging alerts under constrained resources. Do not make autonomous budget, legal, or life-safety decisions.

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.

Prepare privacy-preserving, source-traceable threat intelligence for approved peer sharing. Use when converting incident or pattern evidence into a shareable defensive signal. Do not rely on heuristic anonymization alone or claim compliance without specialist review.

Create a durable session handoff or exact-thread closeout receipt. Use when work pauses, crosses machines or agent hosts, or needs completion verified before archiving. Record evidence, remaining obligations, and the next action.

OverKill Hill P³ SharePoint List build screenshot auditor. Use when reviewing screenshots of SharePoint Online list settings, column settings, indexed columns, content types, views, or Advanced Settings against a repo schema, build card, runbook, ADR, or CSV header. Also activate when the user says they captured SharePoint build screenshots, asks whether a list or column was configured correctly, points to arrows/markups in images, or needs a defect list before continuing manual SharePoint build work. This is the authoritative screenshot-review skill for this repo's UI-only SharePoint build process.

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.