All authors
Claude Skills by OKHP3
github.com/OKHP3315 skills3 installs422 views
- Okhp3 Askjamie Extract ClaudeExtract 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...Votes: 0GitHub stars: 3
- Okhp3 Askjamie Gpt BuilderBuild, audit, and improve AskJamie Custom GPTs as calm, architected AI helpdesk experiences. Use this skill for GPT ideas, instructions, knowledge, tools, walkthroughs, decision trees, diagrams, evals, and packaging tuned to AskJamie's role as the interpretive intelligence layer between strategy and execution.Votes: 0GitHub stars: 3
- Okhp3 Askjamie Gpt ReadinessAssess an incomplete or newly proposed AskJamie lens or Custom GPT for build readiness. Use when a user has an AskJamie idea, partial notes, pasted conversation, draft instructions, knowledge files, or unfinished assistant and needs an evidence inventory, explicit gaps, targeted elicitation, a readiness score, or a handoff to okhp3-askjamie-gpt-builder.Votes: 0GitHub stars: 3
- Okhp3 Askjamie Repo CreatorCreate 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.Votes: 0GitHub stars: 3
- Okhp3 Askjamie Repo OrganizerOverKill 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...Votes: 0GitHub stars: 3
- Okhp3 Askjamie Style RegistryOverKill 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...Votes: 0GitHub stars: 3
- Okhp3 Askjamie Thread ContextExtract 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...Votes: 0GitHub stars: 3
- Api DesignDesigns an interface other people will depend on — REST endpoints, RPC methods, library functions, CLI commands, event payloads. Use this whenever the user is adding a public endpoint, designing a library's surface, defining a message contract, or asking how something should be called. Also use before implementing anything other teams or external users will consume, because the cost of changing it later is the whole point. For implementing against an existing interface, use feature-implementa...Votes: 0GitHub stars: 3
- Api DocumentationDocuments an interface others will call — endpoints, SDK methods, CLI commands, and their parameters, errors, and limits. Use this whenever the user needs API docs, an OpenAPI spec, reference documentation, docstrings for a public library, or has an interface that people keep asking questions about. For designing the interface itself, use api-design; for prose guides and READMEs, use markdown-docs.Votes: 0GitHub stars: 3
- Auth DesignDesigns how a system knows who someone is and what they may do — login, sessions, tokens, roles, and permission checks. Use this whenever the user is building login or signup, adding roles or permissions, choosing between sessions and JWTs, integrating OAuth or SSO, or asking how to protect an endpoint. For finding authorization bugs in code that exists, use security-analysis.Votes: 0GitHub stars: 3
- Browser TestingExplores and tests web applications, prepares forms for review, and writes or debugs end-to-end browser tests with Playwright, Cypress, or Selenium. Use for UI-only bugs, exploratory website testing, observed-first Playwright test generation, local webapp debugging, responsive checks, and flaky browser suites. Covers selectors, state-based waiting, isolated data, and failure evidence. For logic below the UI, use unit-testing.Votes: 0GitHub stars: 3
- C4 Codebase ArchitectureHelps an agent inspect a repository and produce C4 architecture documentation. Use this when reverse engineering a codebase, documenting system context, containers, components, or clarifying architecture from code and infrastructure.Votes: 0GitHub stars: 3
- Code AnalysisBuilds an understanding of a whole codebase or subsystem — what it does, how it is structured, where the risk and complexity concentrate, and reports it as a map someone can act on. Use this whenever the user is new to a repo, inherits unfamiliar code, asks how something works end to end, wants an architecture overview or health assessment, or is deciding whether to refactor, extend, or replace. For reviewing a specific change, use code-review.Votes: 0GitHub stars: 3
- Code LintingSets up, fixes, or tunes linting and formatting for a project in any language — Python, JavaScript/TypeScript, Go, Rust, Java/Kotlin, Ruby, shell, SQL, Markdown, YAML, Dockerfiles, Terraform. Use this whenever the user mentions linting, formatting, style checks, pre-commit hooks, a noisy or failing lint job, or asks to clean up or standardise a codebase, and also when a project has no linter at all and work is starting on it. For reviewing a specific change, use code-review; linting is what m...Votes: 0GitHub stars: 3
- Code ReviewReviews a change — a diff, a PR, a branch, or uncommitted work — for correctness, risk, and maintainability, and reports findings ranked by severity. Use this whenever the user asks you to review, check over, or give feedback on code they or someone else wrote, mentions a pull request, or says a change is "ready", even if they only ask "does this look ok?". For examining a whole codebase rather than a change, use code-analysis; for vulnerabilities specifically, use security-analysis.Votes: 0GitHub stars: 3
- Codebase ArchitectureDesigns, deepens, and hardens TypeScript codebase architecture in three modes: folder structures, module contracts, and middleware pipelines for a new app; domain-informed deepening of existing code; and the guardrail tooling, CI gates, and wayfinding that stop a structure decaying. Use when setting up project structure, organizing a monorepo, designing backend modules, writing an architecture brief, recovering domain terminology, recording an architecture decision, or asking "how should I st...Votes: 0GitHub stars: 3
- Codebase DiscoveryExtract domain, architecture, business rules, workflows and a business glossary from an existing (often poorly-documented) codebase, then validate the findings with a senior BA/Product Owner one question at a time. Produces onboarding-grade docs under docs/ that give a new team member — human or AI — enough context to be productive, ready for harness engineering / Spec Kit. Use when onboarding onto an unfamiliar codebase, reverse-engineering business knowledge, reconstructing lost documentati...Votes: 0GitHub stars: 3
- Copilot Instructions BlueprintTechnology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.Votes: 0GitHub stars: 3
- Create SpecificationCreate a new specification file for the solution, optimized for Generative AI consumption.Votes: 0GitHub stars: 3
- Custom Instructions From CodebaseMigration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.Votes: 0GitHub stars: 3
- Data Migration Best PracticesOperational data migration guidance. Use when moving or transforming persisted data between schemas, databases, services, or storage technologies; running large backfills; applying expand-and-contract schema changes; combining snapshots with live CDC/events; designing resumable batches and checkpoints; reconciling source and target; or planning cutover, rollback, and repair.Votes: 0GitHub stars: 3
- Data MigrationChanges a schema or moves data in production without downtime or loss — column changes, backfills, table splits, and system-to-system moves. Use this whenever the user is writing a migration, altering a table, backfilling data, renaming a column, or moving data between systems. Treat it as required reading before any migration runs against a database with real data. For designing the schema, use data-modeling.Votes: 0GitHub stars: 3
- Ddd Best PracticesDomain-Driven Design guidance for modeling complex domains. Use when designing Bounded Contexts or Subdomains, discovering Aggregate boundaries from invariants and transactions, defining Aggregate Roots, designing Domain Events, typed domain failures, or repository contracts, choosing exception vs Result/Either/Option semantics, choosing Repository vs DAO/query service/gateway, splitting oversized Aggregates, coordinating cross-Aggregate consistency, applying Context Mapping patterns, impleme...Votes: 0GitHub stars: 3
- Dependency AuditAssesses what a project depends on — known vulnerabilities, licence obligations, abandoned packages, and supply chain risk. Use this whenever the user asks what their dependencies look like, mentions a CVE or security advisory, needs a licence review, is evaluating whether to adopt a library, or has a dependency tree nobody has looked at in years. For performing the upgrades this identifies, use dependency-upgrade.Votes: 0GitHub stars: 3
- Deployment StrategiesGets a change into production safely — blue-green, canary, rolling, feature flags, and the rollback that makes each of them safe. Use this whenever the user is planning a release, asks how to deploy without downtime, mentions canary or blue-green, is adding a feature flag, or is nervous about a risky change going out. For deploying an AI agent specifically, use agent-deployment; for the pipeline that runs the deploy, use ci-pipelines.Votes: 0GitHub stars: 3
- DiagrammingDraws architecture and flow diagrams as code — Mermaid, C4, sequence, ER, and state diagrams that stay in version control and do not go stale. Use this whenever the user asks for a diagram, wants to visualise an architecture or flow, mentions Mermaid or C4, or is explaining a system that would be clearer drawn. For the prose around the diagram, use markdown-docs; for charts of quantitative data, use the dataviz guidance.Votes: 0GitHub stars: 3
- Find SkillsHelps agents discover, evaluate, and recommend installable agent skills when a task may be better handled by a specialized skill. Use when users ask how to do a specialized task, whether a skill exists, or how to extend agent capabilities.Votes: 0GitHub stars: 3
- Integration TestingTests that components work together — service against real database, API against real dependencies, module against module. Use this whenever the user mentions integration tests, testing against a real database or queue, contract testing between services, or has unit tests passing while the system is still broken. For testing one unit in isolation, use unit-testing; for driving a real browser, use browser-testing.Votes: 0GitHub stars: 3
- Load TestingMeasures how a system behaves under load and finds where it breaks — throughput ceilings, latency under concurrency, and failure modes at saturation. Use this whenever the user mentions load testing, stress testing, benchmarking, capacity planning, an upcoming traffic spike, or asks how many users the system can handle. For making already-identified slowness faster, use performance-profiling.Votes: 0GitHub stars: 3
- Log AnalysisExtracts an answer from logs, traces, or metrics — finding the relevant lines in volume, correlating across services, and telling signal from noise. Use this whenever the user points at a log file, asks what happened at a particular time, mentions grepping logs, wants to know how often something occurs, or is trying to reconstruct a sequence of events across services. For fixing what the logs reveal, use debugging; for the write-up afterwards, use root-cause-analysis.Votes: 0GitHub stars: 3
- Markdown DocsWrites or restructures project documentation in Markdown — READMEs, guides, references, runbooks, architecture notes — organised around what the reader is trying to do. Use this whenever the user asks for a README, docs, a guide, a runbook, or says their documentation is out of date, missing, or unhelpful, and also after building something substantial that nobody else could pick up without a written explanation.Votes: 0GitHub stars: 3
- Refactoring Best PracticesSafe refactoring guidance for legacy and existing codebases. Use when improving design without changing behavior, creating seams around hard dependencies, migrating null/string/generic exceptions to typed failure contracts, extracting a repository from direct SQL/ORM access, introducing Domain Events into legacy workflows, adding characterization tests, splitting large classes or methods, introducing value objects, replacing conditionals, or incrementally evolving code under risk.Votes: 0GitHub stars: 3
- Rest Api Best PracticesREST API design guidance. Use when designing or reviewing REST endpoints, choosing HTTP methods and status codes, defining URL structure and naming conventions, formatting error responses, implementing pagination or filtering, versioning an API, securing endpoints with authentication or rate limiting, or reviewing whether an API exposes domain capabilities rather than raw CRUD operations.Votes: 0GitHub stars: 3
- Secrets ManagementHandles credentials safely through their whole life — where they live, how code gets them, how they rotate, and what to do when one leaks. Use this whenever the user is adding an API key, database password, token, or certificate, mentions a secrets manager or vault, asks how to store credentials, or has committed a secret to git. For finding exposed secrets during a code review, use security-analysis.Votes: 0GitHub stars: 3
- Security AnalysisReviews code or a change for exploitable vulnerabilities — injection, auth and access-control gaps, secret exposure, unsafe deserialization, SSRF, path traversal, and reports them with the concrete attack path. Use this whenever the user asks about security, vulnerabilities, hardening, or a security review, and also proactively when a change touches authentication, authorization, user input handling, file paths, subprocess calls, deserialization, or credentials. For general correctness review...Votes: 0GitHub stars: 3
- Software Architecture AnalysisUse this skill to reverse-engineer an existing software system, map itsVotes: 0GitHub stars: 3
- Tdd Best PracticesTest-Driven Development guidance. Use when writing tests before implementation, applying Red-Green-Refactor, testing Value Object contracts, typed domain failures/Results, DDD Aggregates, Domain Events/subscribers, transaction or cache boundaries, data migrations/backfills, Criteria/query adapters, repository contracts or persistence adapters, choosing between test doubles, deciding test granularity, reviewing test suite quality, or diagnosing brittle tests.Votes: 0GitHub stars: 3
- Threat ModelingWorks out what could go wrong in a system's design before it is built — who would attack it, how, and which defences are worth having. Use this whenever the user is designing a system that handles sensitive data, money, or authentication, asks what the security risks are, mentions threat modeling or STRIDE, or is starting a feature with a meaningful attack surface. This is design-time and systematic; for finding vulnerabilities in code that exists, use security-analysis.Votes: 0GitHub stars: 3
- Unit TestingWrites 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.Votes: 0GitHub stars: 3
- Update SpecificationUpdate an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.Votes: 0GitHub stars: 3
- Vercel React Native SkillsReact 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.Votes: 0GitHub stars: 3
- Workflow Analysis BlueprintComprehensive 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.Votes: 0GitHub stars: 3
- Okhp3 Thread Extract Copilot M365Extract 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...Votes: 0GitHub stars: 3
- Okhp3 Thread Extract GeminiExtract 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...Votes: 0GitHub stars: 3
- Okhp3 Thread Extract Mistral VibeExtract 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...Votes: 0GitHub stars: 3
- Okhp3 Thread Extract PerplexityExtract 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. ...Votes: 0GitHub stars: 3
- Okhp3 Copilot Studio Skill FoundryDesign, 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.Votes: 0GitHub stars: 3
- Okhp3 Cowork Commitment TrackerFind 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.Votes: 0GitHub stars: 3
- Okhp3 Cowork Daily Execution BriefBuild 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.Votes: 0GitHub stars: 3
- Okhp3 Cowork Decision RecordDraft 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.Votes: 0GitHub stars: 3