원클릭으로 Manus에서 모든 스킬 실행

okhp3-process-capture

스타2

포크1

업데이트2026년 7월 24일 17:55

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).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

OKHP3

OKHP3/skillz

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

okhp3-process-capture

The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.

Process

Extract the pattern. From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.
Assess readiness. Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?
- Not ready -> write a docs/BACKLOG.md entry (date, task, times observed, candidate family, status: captured). Stop here.
- Ready -> continue to step 3.
Determine target family. Does this fit an existing family (mermaid/, linkedin/, or this repo's own process-capture/), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm.
Produce the skeleton. Frontmatter (name, "pushy" description per skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones).
Update the index. Add the new skill's trigger row to root AGENTS.md, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.

Handoff

A skeleton from this skill is a starting point for skill-creator (the Anthropic example skill, if available) for full authoring, testing, and description-optimization — this skill does intake and structure, not iteration and evals.

About

Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.

이 저장소의 다른 Skills

같은 저장소

okhp3-tradition-observance-calendar

OKHP3/skillz

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 Orthodox), Wikipedia summary fetching for event descriptions, .ics file generation, emoji assignments, holiday filter lists, and session caching strategy. All data sources are free, public, and require no API key. Zero cost. MIT license. Also activate when a user asks to "add holidays to my calendar app", "download religious observances as .ics", "show Jewish/Islamic/Christian holidays for a year", or compute Easter dates -- including when they ask for "all three faiths" or any single tradition's observance list.

2026-07-242

okhp3-verse-lookup

OKHP3/skillz

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.

2026-07-242

okhp3-custom-gpt-builder

OKHP3/skillz

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.

2026-07-242

okhp3-gpt-skill-conversion-plan

OKHP3/skillz

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.

2026-07-242

okhp3-foundry-repo-creator

OKHP3/skillz

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.

2026-07-242

okhp3-notion-capture-router

OKHP3/skillz

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, Perplexity, Copilot, Gemini, PDF, Markdown, transcript, knowledge-base, Notion API, Notion connector, page, database, data source, or thread-export requests, even when the user does not name this skill.

2026-07-242

name	okhp3-process-capture
description	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).
license	MIT
metadata	{"author":"Jamie Hill (OverKill Hill P³)","version":"1.1.0","category":"meta-tooling","origin":"okhp3/skillz","homepage":"https://overkillhill.com","author-github":"https://github.com/OKHP3","in_scope":"Recurring-task recognition, bounded backlog capture, and skill-skeleton handoff.","out_of_scope":"Full skill authoring, unapproved repository edits, and treating one-off work as a durable workflow."}

okhp3-process-capture

The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.

Process

Extract the pattern. From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.
Assess readiness. Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?
- Not ready -> write a docs/BACKLOG.md entry (date, task, times observed, candidate family, status: captured). Stop here.
- Ready -> continue to step 3.
Determine target family. Does this fit an existing family (mermaid/, linkedin/, or this repo's own process-capture/), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm.
Produce the skeleton. Frontmatter (name, "pushy" description per skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones).
Update the index. Add the new skill's trigger row to root AGENTS.md, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.

Handoff

About

Built by Jamie Hill · OverKill Hill P³ Published at github.com/OKHP3 Part of the OKHP3/skillz Agent Skill library. MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.