Home
Softono
ai-skills

ai-skills

Open source PowerShell
Website GitHub
11
Stars
2
Forks
0
Issues
3
Watchers
1 week
Last Commit
AI Tools RPA

About ai-skills

AI SKILL.md files

Platforms

Web Self-hosted

Languages

PowerShell

Links

Website Source Code
f
Published by
fernandotellado
Visit View Profile

README.md

View on GitHub

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:

Start Here If You Are New

Use this repo in this order:

  1. Pick the platform you want to use first.
  2. Open that platform's skill folder.
  3. Read the skill README.md before anything else.
  4. Open the main source file for that skill.
  5. Copy the skill into the target app using the platform steps below.
  6. 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:

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

How to implement it:

  1. Open Claude.
  2. If you use packaged imports, import the .skill file from that skill folder.
  3. If you manage Claude skills manually, place the skill files in the local Claude skills location you use on your machine.
  4. Refresh Claude or start a new chat so the skill is available.
  5. 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:

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

ChatGPT

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

What to open:

  1. Open the skill folder.
  2. Read README.md.
  3. Open instructions.md.

How to implement it with a custom GPT:

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

How to implement it with Custom Instructions:

  1. Open ChatGPT.
  2. Open Settings.
  3. Open Custom Instructions.
  4. Copy the full contents of instructions.md.
  5. Paste it into the instruction area that controls how ChatGPT should respond.
  6. Save changes.
  7. 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:

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

How to implement it:

  1. Decide where you want Copilot to use the skill:
    • repo level instructions
    • a prompt file
    • a one time chat paste
  2. Copy the full contents of the skill instruction file.
  3. Paste it into the Copilot surface you are using.
  4. If the target repo already has instructions, merge carefully instead of overwriting unrelated rules.
  5. 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:

Gemini

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

What to open:

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

How to implement it:

  1. Open Gemini.
  2. Create or edit the Gem or reusable assistant setup you want to use.
  3. Copy the full contents of the skill instruction file.
  4. Paste that content into the Gemini instruction area.
  5. Save the Gem or assistant.
  6. 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:

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

How to implement it:

  1. Open Perplexity.
  2. Create a new skill or edit an existing one.
  3. Copy the full contents of the source file, or upload the packaged artifact if that skill README calls for it.
  4. Save the skill.
  5. 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:

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

How to implement it:

  1. Open Cursor.
  2. Decide whether the instructions belong in project rules, user rules, or a one time chat context.
  3. Copy the full contents of the skill instruction file.
  4. Paste it into the chosen Cursor rule or instruction surface.
  5. 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 equity, macro, and 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:

Perplexity Skills

No Perplexity skills added yet.

Platform folder:

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

Repository Structure

  • shared/: repo-wide guidance, standards, and naming rules
  • templates/: starter templates for new skills
  • claude/: Claude-specific skills, scripts, and metadata
  • chatgpt/: ChatGPT-specific instructions, prompts, and schemas
  • copilot/: GitHub Copilot instructions and prompts
  • gemini/: Gemini-specific instructions and Gem-ready skill content
  • perplexity/: Perplexity-specific skill files and setup notes
  • cursor/: Cursor-specific rules and coding assistant instructions

Working Model

  1. Pick the target platform first.
  2. Write the skill in that platform's folder as the source of truth.
  3. Use shared/ for naming, structure, and repo-level guidance only.
  4. Record checks with templates/test-template.md.

For Claude skills, keep tracked shipped history in completed-changes.md and keep local future-upgrades.md files focused on future planning only.

Spec Workflow

Use specs/ for non-trivial repo work such as shared conventions, packaging rules, cross-skill changes, or shared script updates.

Skip it for small single-skill wording edits or minor doc cleanup.

Start Here