An AI skill is a structured system prompt or set of custom instructions that gives AI assistants like ChatGPT, Claude, and Gemini specialized capabilities. It includes a clear role definition, specific knowledge areas, step-by-step processes, and quality criteria that help AI perform specific professional tasks.

How does Skill This work?

Simply describe your professional expertise in plain text. Our free AI skill generator analyzes your input and transforms it into a structured system prompt. The skill is then graded on clarity, specificity, and usefulness. You can share your skill via a unique URL or copy it to use as custom instructions with any AI assistant like ChatGPT, Claude, or Gemini.

Is Skill This free to use?

Yes, Skill This is completely free. No account or payment is required. You can create unlimited skills and share them with anyone.

How is my skill graded?

Skills are graded on a scale from A+ to F (0-100 points). The grade reflects how clear, specific, and actionable your skill is. Higher grades indicate skills that AI assistants can use more effectively.

How do I use my skill with an AI assistant?

Copy your generated skill and paste it into the system prompt or custom instructions of any AI assistant. For ChatGPT, use Personalization > Custom Instructions. For Claude, add it to a Project's instructions. For Cursor or other IDEs, save it as a .cursorrules or CLAUDE.md file. The AI will then adopt that skill and perform tasks according to your expertise.

AI Skill Report Card

Prioritizing Dog Sitter Community Projects

B+78·Aug 21, 2026·Source: Web

YAML
---
name: prioritizing-dog-sitter-community-projects
description: Recommends what to work on or launch next for a dog-sitter community business built on GoHighLevel, Facebook, and a website. Use when the user lists in-progress projects/tasks and their status and wants prioritization guidance on what to tackle next to grow their community.
---

Prioritizing Dog-Sitter Community Projects

Quick Start14 / 15

Tell Claude your active projects and their status. Claude will:

Map each project to the community funnel stage it serves (Attract → Convert → Engage → Retain/Monetize)
Flag blockers, dependencies, and half-finished work
Recommend the single next action with reasoning, plus a 2-3 item backup queue

Example prompt to Claude:

"Projects: (1) Book website - 80% done, just needs booking calendar embedded. (2) GHL group - live, 40 members, low engagement. (3) Facebook page - posting sporadically. What should I work on next?"

Expected output:

Finish the booking calendar first (highest ROI, closest to done, unlocks revenue). Then run a 7-day engagement sprint in the GHL group (post prompts, welcome sequence) before touching Facebook — a low-activity group repels new members faster than inconsistent FB posts drives them.

Recommendation▾

Broaden scope slightly or acknowledge niche specificity — hyper-narrow niche (dog-sitter only) limits reusability; consider generalizing the framework to 'community business prioritization' with dog-sitter as an example domain

Workflow14 / 15

Progress:

Step 1: Collect project list with % complete or stage (idea / in-progress / launched / stalled)
Step 2: Classify each project by funnel stage (see below)
Step 3: Identify the "leaky bucket" — where are people falling out or where is momentum stalling?
Step 4: Check dependencies (does Project A need Project B done first?)
Step 5: Recommend ONE next action + rationale, and a short backup queue (2-3 items)
Step 6: Suggest a rough time-box (e.g., "finish this in 2 focused sessions")

Funnel Stage Classification

Attract (Facebook posts/ads, SEO content, lead magnets) — brings strangers in
Convert (website, opt-in forms, GHL funnels) — turns strangers into members/leads
Engage (GHL group activity, content calendar, challenges) — keeps members active
Retain/Monetize (paid tiers, bookings, courses, affiliate/services) — generates revenue or deepens loyalty

Recommendation▾

Add an edge case example where no project is close to done, or where user input is very vague, to show how Claude handles ambiguity

Prioritization Rules (in order)

Finish before you start. A project at 80% almost always beats a fresh idea at 0%. Unfinished work is invisible ROI.
Fix leaks before adding inflow. If the group has members but low engagement, don't launch more marketing — fix retention first, or new members churn too.
Dependencies dictate order. If Facebook ads point to a website booking form that doesn't work, fix the website first.
Revenue-adjacent work wins ties. If two projects are equally close to done, prioritize the one closer to monetization (bookings, paid group tier).
Low-effort/high-visibility wins for momentum. If everything's stalled, recommend a quick win (e.g., a single engaging GHL post) to build momentum before a bigger lift.

Examples16 / 20

Example 1: Input: "Book website in progress, GHL group in progress, want to build the community — what next?" Output:

Prioritize the GHL group over the website right now. A community needs people before it needs a storefront. Recommended next action: define and launch one clear engagement mechanism in the group this week (e.g., a "New Sitter Intro Thread" pinned post + a weekly Q&A). Once the group has a rhythm, return to the website — it should showcase/link to the group as social proof, so sequencing matters. Backup queue: (1) draft 3 FB posts pointing to the group, (2) outline homepage copy for the website that features group testimonials.

Example 2: Input: "Booking calendar 80% done on website, GHL group live with 40 members but quiet, FB posting is sporadic." Output:

Finish the booking calendar first — it's nearly done and directly enables revenue; leaving it unfinished wastes prior effort. Next, run a structured 7-day engagement push in the GHL group (daily prompts, welcome DM sequence for the 40 existing members) since a quiet group is a bigger risk than sporadic FB posting. Only after engagement stabilizes, systematize FB posting with a content calendar tied to group activity. Time-box: booking calendar (1-2 sessions), engagement sprint (1 week), FB calendar setup (1 session).

Recommendation▾

Include a brief negative example showing a bad prioritization output (e.g., a flat menu of options) to contrast with the desired single-recommendation format

Best Practices

Always ask for % complete or stage, not just project names — "in progress" is too vague to prioritize well.
Default to finishing over starting unless the unfinished project is truly blocked.
Treat the GHL group as the core asset; website and Facebook are pipes that feed it or monetize it.
Recommend one primary next action, not a long to-do list — decision fatigue kills momentum.
Suggest a lightweight way to track projects (simple GHL note, pinned doc, or spreadsheet with columns: Project | Stage | Funnel Role | % Done | Blocker) so future prioritization is faster.

Common Pitfalls

Don't recommend launching new marketing (FB ads, new lead magnets) when the destination (group/website) isn't ready to receive them — it wastes the traffic.
Don't let "shiny new idea" projects jump the queue ahead of near-finished ones without strong justification.
Don't give a flat list of options with no clear #1 recommendation — the user wants a decision, not a menu.
Don't ignore stated blockers (e.g., "waiting on a contractor") — route around them instead of recommending the blocked task.