Topics

#ai-skills #ai-workflows #automation #chatgpt #claude-skills #copilot #custom-gpt #github-copilot #github-spec-kit #llm #openai #powershell #prompt-engineering #rpa #system-prompts

Language breakdown

PowerShell 65.5%

Python 34.5%

▸ Files click to expand

README

AI Skills

A shared home for AI skills organized by platform. Skills live under the platform they are written for. Shared docs cover conventions and repo guidance only.

See completed-projects.md for completed repo additions. See completed-upgrades.md for completed repo upgrades. See changelog.md for the repo change history. See skill-improvement-assessment.md for the current skill quality review.

Current repo social preview asset:

.github/github-social-preview.jpg

Start Here If You Are New

Use this repo in this order:

Pick the platform you want to use first.
Open that platform's skill folder.
Read the skill README.md before anything else.
Open the main source file for that skill.
Copy the skill into the target app using the platform steps below.
Test it with one simple prompt before relying on it.

If you are not sure which file is the source of truth:

Claude skills usually use SKILL.md
ChatGPT skills usually use instructions.md
Copilot skills should use the main instruction file stored in that skill folder
Gemini skills will usually use instructions.md
Perplexity skills will usually use SKILL.md
Cursor skills will usually use instructions.md

How To Implement A Skill In Each Ecosystem

These steps are written for a first time user.

Claude

Claude skills in this repo live under claude/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open SKILL.md.
If the folder includes a .skill file, that is the packaged Claude import file.

How to implement it:

Open Claude.
If you use packaged imports, import the .skill file from that skill folder.
If you manage Claude skills manually, place the skill files in the local Claude skills location you use on your machine.
Refresh Claude or start a new chat so the skill is available.
Test it with one of the example prompts from the skill README.md or SKILL.md.

What to expect:

SKILL.md is the editable source
.skill is the install or import artifact
README.md explains what the skill does and how to test it

If you change a Claude skill:

Edit SKILL.md first.
Update README.md if the setup or behavior changed.
Rebuild the .skill package so the import file matches the source.
Test again in Claude.

ChatGPT

ChatGPT skills in this repo live under chatgpt/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open instructions.md.

How to implement it with a custom GPT:

Open ChatGPT.
Create a new custom GPT, or edit an existing one.
Copy the full contents of instructions.md.
Paste that content into the GPT instructions area.
Save the GPT.
Test it with one of the prompts from the skill README.md.

How to implement it with Custom Instructions:

Open ChatGPT.
Open Settings.
Open Custom Instructions.
Copy the full contents of instructions.md.
Paste it into the instruction area that controls how ChatGPT should respond.
Save changes.
Start a new chat and test it.

What to expect:

instructions.md is the editable source
README.md explains where to paste it and how to test it
A custom GPT is usually the safer option because it does not affect unrelated chats

GitHub Copilot

Copilot skills in this repo live under copilot/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open the main instruction file for that skill, usually instructions.md.

How to implement it:

Decide where you want Copilot to use the skill:

- repo level instructions - a prompt file - a one time chat paste

Copy the full contents of the skill instruction file.
Paste it into the Copilot surface you are using.
If the target repo already has instructions, merge carefully instead of overwriting unrelated rules.
Test it with a small real task.

What to expect:

Copilot skills are instruction driven, not packaged like Claude .skill files
The exact place you paste the instructions depends on the Copilot surface you use
The skill folder should still contain a beginner friendly README.md and one clear source file

Current example:

copilot/skills/pr-review

Gemini

Gemini skills in this repo will live under gemini/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open the main instruction file, usually instructions.md.

How to implement it:

Open Gemini.
Create or edit the Gem or reusable assistant setup you want to use.
Copy the full contents of the skill instruction file.
Paste that content into the Gemini instruction area.
Save the Gem or assistant.
Test it with one simple prompt from the skill README.

What to expect:

Gemini skills are instruction driven
The skill folder should explain the exact Gemini surface it targets
This repo does not yet include a live Gemini skill example

Perplexity

Perplexity skills in this repo will live under perplexity/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open the main source file, usually SKILL.md.

How to implement it:

Open Perplexity.
Create a new skill or edit an existing one.
Copy the full contents of the source file, or upload the packaged artifact if that skill README calls for it.
Save the skill.
Test it with one prompt from the skill README.

What to expect:

Perplexity is the closest match to a true skill workflow outside Claude in this repo plan
The skill README should say whether to paste Markdown directly or upload a file
This repo does not yet include a live Perplexity skill example

Cursor

Cursor skills in this repo will live under cursor/skills/<skill-name>/.

What to open:

Open the skill folder.
Read README.md.
Open the main instruction file, usually instructions.md.

How to implement it:

Open Cursor.
Decide whether the instructions belong in project rules, user rules, or a one time chat context.
Copy the full contents of the skill instruction file.
Paste it into the chosen Cursor rule or instruction surface.
Test it on a small real coding task.

What to expect:

Cursor skills are reusable coding rules rather than packaged skill files
The skill folder should say whether the instructions are meant for project scope or user scope

Current examples:

Platform Quick Map

| Platform | Skill folder | Main source file | How you usually apply it | | ----- | ----- | ----- | ----- | | Claude | claude/skills/<skill-name>/ | SKILL.md | Import or install the .skill package, then test in Claude | | ChatGPT | chatgpt/skills/<skill-name>/ | instructions.md | Paste into a custom GPT or ChatGPT Custom Instructions | | Copilot | copilot/skills/<skill-name>/ | platform instruction file | Paste into the Copilot instruction surface used by that repo or workflow | | Gemini | gemini/skills/<skill-name>/ | instructions.md | Paste into a Gemini Gem or equivalent Gemini instruction surface | | Perplexity | perplexity/skills/<skill-name>/ | SKILL.md | Paste Markdown directly or upload the skill file, depending on the skill README | | Cursor | cursor/skills/<skill-name>/ | instructions.md | Paste into project rules, user rules, or chat context in Cursor |

Claude Skills

| Skill | Description | | ----- | ----------- | | alpaca-trading | Safe workflows for the Trading repo and Alpaca-related automation | | blog-post | Write blog posts in Mick's voice for mickitblog.blogspot.com | | blog-to-social | Convert a finished blog post into Facebook, X, and LinkedIn posts in one pass | | container-home | Off-grid shipping container lake home project in Dover, Tennessee | | crypto-listings | Track recent and upcoming cryptocurrency listings across major exchanges | | crypto-research | Structured due diligence on a specific cryptocurrency | | facebook-post | Write and polish Facebook posts in Mick's voice with audience control, media aware captions, and X repurpose support | | facebook-reply | Write Facebook replies with tone control, context awareness, and batch thread handling | | fitness-log | Track workouts, analyze training trends, plan progression blocks, and generate fitness Facebook posts | | fitness-programming | Build structured training blocks with presets, recovery adjustments, benchmark reviews, and season planning | | food-analyzer | Analyze foods, compare meals, and score nutrition fit with confidence, timing, and goal aware context | | github-readme | Write polished README.md files in a direct, technical, practitioner-focused voice | | github-repo-architect | Turn a rough project idea into a complete GitHub repository architecture | | github-social-preview | Generate branded GitHub social previews with themes, smarter fitting, and optional visual assets | | idea-forge | Run any raw idea through a five-stage R&D pipeline and produce a scored invention plan with architecture, monetization paths, and an MVP roadmap | | linkedin-post | Write LinkedIn posts with mode control, credibility checks, CTA styles, and audience variants | | market-brief | Generate current morning market briefs for Mick's indices, commodities, currencies, macro, and expanded crypto watchlist | | med-vault | Track medications, review interactions, generate schedules, and run OCR-assisted intake under strict medical safety boundaries | | n8n-workflow | Design, build, and troubleshoot n8n workflows on a self-hosted Proxmox stack | | obsidian-workout-export | Export logged workout sessions into Obsidian-ready Markdown files | | patentforge-provisional | Turn an invention idea into a structured disclosure, prior art search plan, claim candidates, and provisional draft package | | photo-rename | Rename photos with consistent filename rules, confidence handling, batch review, and GPS-aware fallback logic | | pihole-blocklist | Evaluate, categorize, and document new Pi-hole blocklist sources | | pihole-csv-analyzer | Analyze Pi-hole CSV exports and generate practical cleanup recommendations | | powershell-refactor | Simplify, tighten, and standardize existing PowerShell scripts without changing the intended behavior | | proxmox-lxc | Deploy and configure Proxmox LXC containers on a self-hosted homelab stack | | resume-writer | Rewrite, audit, score, and target resumes with fit scoring, recruiter skim views, and interview handoff | | spec-writer | Generate numbered repo spec folders with clear requirements, implementation plans, and task lists | | travel-itinerary | Plan and export travel itineraries with templates, route notes, realistic pacing, and budget visibility | | travel-planning | Plan solo travel with destination scoring, style presets, booking triage, and itinerary handoff | | travel-research | Compare destinations with deeper scoring across budget, climate, logistics, activity fit, and seasonal tradeoffs | | website-content | Write and update content for mickpletcher.com | | x-post | Write X posts on tech, PowerShell, IT automation, and fitness topics | | x-reply | Write replies to replies on X |

ChatGPT Skills

| Skill | Description | | ----- | ----------- | | food-analyzer | Analyze food photos and nutrition labels |

GitHub Skills

| Skill | Description | | ----- | ----------- | | commit-message-writer | Write consistent, ready to paste commit messages from diffs or work summaries | | pr-review | Review pull requests for regressions, practical risk, and missing tests | | project-handoff | Create durable handoff docs such as assessment, project analysis, or session context files | | readme-sync | Reconcile README claims with actual code, scripts, commands, tests, and outputs | | repo-cleanup-audit | Classify stale files, generated artifacts, historical records, and source of truth files before cleanup | | spec-scaffold | Generate numbered spec folders with requirements, plan, and task files |

Gemini Skills

No Gemini skills added yet.

Platform folder:

gemini/README.md

Perplexity Skills

No Perplexity skills added yet.

Platform folder:

perplexity/README.md

Cursor Skills

| Skill | Description | | ----- | ----------- | | pr-review | Review pull requests and diffs for regressions, risk, and missing tests | | workflow-debugger | Debug CI failures, local repro paths, and targeted fix loops | | repo-assessment | Produce durable repo handoff docs with current state, risks, and best next step | | spec-writer | Turn rough repo work into numbered specs with requirements, plan, and tasks |