--- name: Check Resale Rights category: legal works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original (built for this library; guardrails per the TemplatedAI standard) tested: no --- # Check Resale Rights ## What it does Sorts a pile of digital files you're thinking of selling — a PLR bundle, a course pack, templates, ebooks, a folder someone shared with you — into what you can document rights for, what you only *believe* you have rights to, and what is obviously someone else's commercial property. The output is a "do not sell until resolved" list, not permission. ## When to use it - You bought a bundle advertised with "resell rights" and want to sell it on - Someone shared a big drive folder and suggested you could make money from it - Before listing anything on Gumroad, Etsy, Shopify, or your own site that you didn't make yourself ## The skill ``` Act as a rights librarian doing an inventory. HARD RULES: you can NEVER confirm that I have the right to sell something — only a written licence and, for real stakes, a lawyer can do that; never invent or cite statutes, case law, or licence terms; treat "the seller said so" and "it was in the bundle" as unverified claims, not as rights; if I can't produce a written licence for an item, it goes in the unresolved pile no matter how confident I sound. What I have: [LIST THE ITEMS / FOLDERS / PRODUCT TYPES — be specific: "42 ebooks, 300 Canva templates, a marketing course"] Where it came from: [WHO SOLD OR SHARED IT, WHAT THEY CLAIMED, WHAT I PAID] Licence documents I actually hold: [PASTE OR DESCRIBE — or "none"] What I want to do with it: [SELL AS-IS / BUNDLE IT / GIVE AWAY / USE IN MY OWN WORK] Sort every item into four piles: 1. DOCUMENTED — I hold a written licence that covers what I want to do. For each, quote the clause that covers it, and name any condition attached (attribution, no-modification, minimum price, no giveaway). 2. CLAIMED BUT UNDOCUMENTED — rights were asserted by a seller but I hold no licence document. Tell me exactly what to request from them, and what a real licence should contain. 3. RECOGNISABLY SOMEONE ELSE'S — commercial books, brand-name courses, character or franchise material, well-known workbooks, comics, films, music. Flag these plainly: mainstream publishers and studios do not licence their catalogue into cheap resale bundles, so a bundle containing them is a warning about the whole bundle. 4. MINE — things I actually made. Point out that this is the only pile with no rights problem at all. Then give me: - THE DO-NOT-SELL LIST: everything from piles 2 and 3, with the one question that would resolve each. - THE PRACTICAL RISKS of selling unresolved items: takedown notices, losing a shop account and its sales history, chargebacks, and being the visible seller when the actual owner comes looking. - THE LAWYER LIST: what only a professional in my jurisdiction can answer if I intend to build a business on any of this. End with: "This is an inventory of your rights questions, not confirmation that you hold any rights." ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - The test that cuts through everything: can you produce the licence document for this specific item? "It came with resell rights" is a sentence, not a licence - Licences attach to individual products, not to bundles — one file's licence says nothing about the file next to it - If pile 3 has anything in it, the honest read is that the whole bundle was assembled by someone who didn't check either ## The honest line Reselling other people's work is a business built on a document you either have or don't. If the answer is "I'm pretty sure it's fine," you're the one carrying the risk — and the pile you made yourself is the only part nobody can take away from you. --- --- name: Vet a Bundle category: security works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original (built for this library; guardrails per the TemplatedAI standard) tested: no --- # Vet a Bundle ## What it does Runs the checks before you pay for a mega-bundle — "100,000 digital products", "thousands of ebooks", "500+ AI prompts", a lifetime course vault — so you find out what you're actually getting while your money is still yours. Built around the three things these listings almost never say out loud: how it's delivered, how much of it is duplicates, and whether it was the seller's to sell. ## When to use it - A bundle is advertised by its item count and a countdown timer - Delivery is "a Google Drive link" and you're not sure that's the same as owning something - Any "lifetime access" offer, before you pay ## The skill ``` Act as a careful buyer helping me check a digital bundle before I pay. Rules: you cannot verify this specific seller or product — you don't have live access, so never tell me a named seller is legitimate or a scam; produce the checks I run myself and what each result would mean. No reassurance: if I describe something that should worry me, say so plainly. The offer: [WHAT'S ADVERTISED — item count, price, claims] The seller: [WHERE THEY'RE SELLING — platform, social account, how long they've existed as far as I can tell] How it's delivered: [DRIVE LINK / DOWNLOAD / MEMBER AREA / UNKNOWN] What I actually want out of it: [THE REAL REASON I'M TEMPTED] Walk me through: 1. DELIVERY: what I truly get. Explain the difference between a file I download and hold, and a shortcut or link to someone else's cloud folder that they can revoke, delete, or lose to a platform ban — and how to tell which one this is BEFORE paying. State plainly whether "lifetime access" can be promised at all under the delivery method described. 2. THE COUNT: how bundle item counts get inflated — duplicated folders, the same file in several categories, near-identical variants, filler nobody made deliberately. Give me the two questions to ask the seller that a padded count can't survive. 3. THE CONTENTS: what to look for in the preview or file list that suggests material the seller had no right to include — commercial books, brand-name courses, franchise or character material, well-known workbooks. Explain what it costs ME to buy a bundle like that: it can vanish, and I can't legally build on it. 4. THE RIGHTS CLAIM: if it promises I can resell it, what document must come with it, and what "resell rights" without a licence file is worth. 5. THE EXIT: refund policy, what the platform's buyer protection actually covers, and what recourse a direct bank or crypto transfer leaves me with (be blunt). 6. THE HONEST TEST: based on what I said I actually want, how many items would I realistically use — and is there a smaller, documented, curated source that covers those? Finish with a plain verdict: what I'd need to confirm before this is a reasonable purchase, and what would make it an obvious no. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Volume is the tell, not the value: a curated ten you use beats a hundred thousand you scroll past once - Ask for one specific item's licence document before buying — a real reseller has it ready, and a padded bundle can't produce it - "Lifetime access" to somebody else's cloud folder lasts exactly as long as their account does - Run this on TemplatedAI too. Everything here is free to read before you commit to anything, every skill's honesty flag says whether it's been tested, and the sources say where a template came from — that's what the checks above should find on a library worth trusting ## The honest line The bundle economy sells the feeling of owning everything. What you usually get is a link to a stranger's messy drive, a lot of duplicates, and no paperwork. Ten minutes of checking beats a refund you'll never get. --- --- name: Test the Demand category: business works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: adapted (viral "daily sales potential" niche lists, rebuilt; invented revenue figures replaced with real demand signals) tested: no --- # Test the Demand ## What it does Finds out whether anyone actually wants your product idea — before you spend a weekend building it. Cheap, honest signals you can gather in a few days: where these people already complain, what they already pay for, and the smallest possible thing you can put in front of them to see if anyone reaches for their wallet. ## When to use it - You have a product idea and no evidence beyond it sounding good - A viral list told you a niche earns $X/day and you want the real answer - You've built things before that nobody bought, and want to stop doing that ## The skill ``` Act as a demand researcher for a one-person business. HARD RULES: never estimate revenue, daily sales, or market size — you have no data and inventing a number is worse than saying nothing; never claim a niche "is profitable"; every signal you propose must be something I can go and OBSERVE this week, with my own eyes, for free. If the honest answer is "you can't know until you ask real people," say that. My product idea: [WHAT IT IS, AND FOR WHOM] Why I think they want it: [MY REAL REASON — a request I got, a problem I had, or "honestly, I just saw it on a list"] Time I can spend testing before building: [HOURS / DAYS] Give me: 1. THE DEMAND QUESTION: rewrite my idea as the one question this test must answer — specific enough that a result would change my mind either way. 2. WHERE THEY ALREADY ARE: the specific places this person shows up with this problem — named forums, subreddits, groups, review sections, search phrases. Tell me what to read, and what evidence of a real problem looks like versus idle chatter. 3. WHAT THEY ALREADY PAY FOR: how to find whether anyone is currently selling something adjacent, and what to read in the reviews of the closest existing product — especially the 1- and 3-star ones, where the gap is. 4. THE FREE VERSION FIRST: the smallest useful thing I can give away this week to see if anyone takes it. What I'd measure, and what a weak result actually looks like so I don't kid myself. 5. THE WALLET TEST: the cheapest honest way to ask for money before it exists — presell to a handful, a waitlist with a real price shown, an offer to the next person who asks me. Write the exact message. 6. THE KILL CRITERIA: define now, before I'm attached, what result means I stop. A test with no failing score isn't a test. Finish by telling me which single step gives the most signal for the least work, and what it can't tell me. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - The strongest signal costs nothing: someone already asked you for this. Start there before anything else - Reviews of the nearest existing product are free market research; the complaints are your feature list - Set the kill criteria before you start. Deciding what counts as failure afterwards is just negotiating with yourself - Pair with Digital Product Outline: test first, scope second. Building first is how the weekend disappears ## The honest line Nobody can tell you a Puppy Care Planner earns $80 a day — not a viral post, not an AI, not me. What you can find out, cheaply, is whether five real people will hand you money before the thing exists. That answer is worth more than any number someone typed into a graphic. --- --- name: Find It Later category: productivity works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: original (built for this library; drawn from real drive folders that had collapsed under their own size) tested: no --- # Find It Later ## What it does Turns a folder you've stopped being able to use — a Drive, a Downloads directory, a photo dump, a course library — into something you can actually find things in: a naming pattern that survives a phone screen, a plan for the duplicates, a shallow structure, and one index file. Not a filing system you'll abandon in a week. ## When to use it - You have hundreds of folders and you search instead of browsing, because browsing stopped working - Names like "Notes (1)", "Notes final", "Notes final v2" have taken over - You know the file is in there somewhere and it's faster to remake it ## The skill ``` Act as a librarian organising a collection someone stopped maintaining. Rules: design for the person I actually am — if a system needs constant upkeep, I won't do it, so keep it lazy-proof; never suggest deleting anything without telling me how to check it's safe first; work only from the folder list I give you and say what you can't tell from names alone. My folder/file list (paste it, or describe the mess honestly): [PASTE NAMES — a screenshot list, a directory listing, or just describe the categories and roughly how many] Where it lives: [DRIVE / DROPBOX / LAPTOP / PHONE] How I mostly open it: [PHONE / DESKTOP / BOTH] What I come here looking for, realistically: [THE 2-3 THINGS] Give me: 1. THE NAMING PATTERN: a rule for naming folders and files that (a) puts the distinguishing word FIRST, because phone and sidebar views truncate the middle and end — "Kids reading — grade 2" and "Kids reading — grade 3" are indistinguishable when both display as "Kids read...", (b) sorts usefully by default, and (c) I can follow half-asleep. Show me my own worst examples renamed. 2. THE DUPLICATE PLAN: from my list, the pairs and near-pairs ("X" and "X (1)", "final" and "final v2"), how to decide which one survives — check dates and sizes first, keep the fuller one, and how to park the losers somewhere reversible instead of deleting outright. 3. THE JUNK PASS: export artefacts and machine suffixes (long timestamp strings, "-001", download numbering) that carry no meaning — a single rule for stripping them. 4. THE SHAPE: a flat-as-possible structure — ideally one level of real categories, with a small number of pinned favourites at the top (a leading character like "_" or "1." forces them to sort first). Tell me honestly which of my current categories are duplicates of each other under different words. 5. THE INDEX: one plain text or doc file living at the top level, listing what each category holds in a line — the thing that makes a big collection usable by anyone including future me. 6. THE 20-MINUTE VERSION: if I only do one pass, which of the above delivers the most findability for the least work. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Front-loading the distinguishing word is the highest-value change on a phone; middles and endings get eaten by truncation - Move duplicates to a "_review" folder rather than deleting — reversible beats tidy, and you'll get braver as nothing breaks - The index file is what turns a hoard into a library; without it, only you know what's in there, and eventually not even you - Do the 20-minute version now and the rest never, rather than planning the perfect system and doing none of it --- --- name: Digital Product Outline category: business works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: adapted (viral "Claude as co-founder" pack, rewritten; "sell by tonight" fantasy removed) tested: no --- # Digital Product Outline ## What it does Scopes a small digital product — a guide, template set, checklist pack, or short course — from a skill you actually have: what's inside section by section, a realistic build plan, honest pricing logic, and a plain listing description. The realistic version of "product by tonight": a *scoped* product by tonight, a finished one after the real hours it takes. ## When to use it - People keep asking you the same question and you keep writing the same long answer - You sell your time and want something that sells without a meeting - You have a half-idea for "a guide or something" and no shape for it ## The skill ``` Act as a digital product editor who scopes small, useful products. Rules: the product must solve ONE specific problem for one specific person — reject my idea if it's "everything I know about X"; be honest about build time — no "finished by tonight" if the outline says otherwise; price on value delivered with plain reasoning, no psychological pricing tricks; never invent demand ("this will sell") — say what would test demand instead. What I know that people ask me for: [THE SKILL / THE QUESTION PEOPLE KEEP BRINGING YOU] Who asks: [WHO THEY ARE] Format I could actually finish: [WRITTEN GUIDE / TEMPLATES / CHECKLISTS / SHORT VIDEO — or "you suggest"] Give me: 1. THE ONE PROBLEM: the specific problem this product solves, in one sentence a buyer would recognize as theirs. If my idea is too broad, narrow it and tell me what you cut. 2. THE CONTENTS: every section/piece, in order, with one line on what each does for the buyer. Small and complete beats big and abandoned. 3. THE BUILD PLAN: the realistic steps and honest hours to finish it, including which parts an AI can draft and which parts need my actual knowledge to be worth paying for. 4. THE PRICE: a number with plain reasoning tied to what the buyer saves or gains — and the cheapest honest way to test it (e.g. presell to 5 people, or offer it to the next person who asks). 5. THE LISTING: a title and description that says what it is and who it's for in plain language. No "ultimate," no "secrets." ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - The question people already ask you is the validated demand — start there, not with a brainstorm - If the AI drafts most of it, buyers can AI it themselves; the parts only you know are the product - Ship the small version first; v2 exists only if v1 sells --- --- name: The Plain Sales Page category: business works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: adapted (viral "8 prompts to sell your skill" pack, rewritten; hype framing removed) tested: no --- # The Plain Sales Page ## What it does Writes the words for your service page — a headline under ten words that needs no further explanation, outcome bullets instead of feature lists, the one objection a skeptical buyer is already thinking answered head-on, and a specific call to action. Copy only; the Landing Page Pack builds the page it goes on. ## When to use it - Your service page describes what you technically do and nobody bites - You're staring at "Welcome to my website" trying to start - Rewriting an existing page that reads like a corporate brochure ## The skill ``` Act as a copywriter who sells services with plain, specific language. Rules: claim only outcomes I can actually deliver and have described — never invent results, statistics, client counts, or testimonials; no hype vocabulary (unlock, transform, skyrocket, game-changer); write like a person who believes the service, not a brochure. My service: [WHAT IT IS, WHO IT HELPS, THE EXACT OUTCOME IT DELIVERS] Proof I actually have: [REAL RESULTS, EXPERIENCE, OR "none yet — new"] Write: 1. A headline under 10 words stating the core outcome — clear enough that it needs no second sentence to land. 2. One supporting line that makes the benefit concrete and removes the main hesitation. 3. 4-5 bullets describing specific outcomes the buyer gets, not the tasks I perform. 4. One short section answering the most obvious objection a skeptical buyer has — honestly, including what this service is NOT for. 5. One clear, specific call to action: what they do, what happens immediately after they do it. If I said "none yet — new," write the page without fake proof; new and honest beats established and invented. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Read the headline out loud; if you'd have to explain it, it isn't done - The "what this is NOT for" line does more converting than any bullet — the right buyers trust a page that turns the wrong ones away - Pair with the Landing Page Pack: this writes the words, that builds the page --- --- name: Price Check category: business works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: adapted (viral "Hormozi prompts" pack, rewritten; persona roleplay removed, frameworks from published books kept) tested: no --- # Price Check ## What it does Audits your price against the value your offer actually delivers and what not-solving costs the buyer — then gives you a three-tier structure and the words to present the price without apologizing for it. ## When to use it - You suspect you're undercharging but can't prove it to yourself - Every discovery call ends in a discount - You're pricing something new and anchoring on competitors instead of value ## The skill ``` Act as a pricing analyst. Principle: the buyer's real alternative is not my competitor — it's the cost of leaving the problem unsolved. Rules: no "charge 10x more" theatrics; every recommendation needs stated reasoning; where you'd need data I didn't give (market rates, my costs), ask or mark it as an assumption. Never invent numbers. What I sell: [DESCRIBE] Current price: [AMOUNT] Competitor range: [RANGE OR "unknown"] My target buyer: [DESCRIBE] Their cost of NOT solving this (money, time, stress — estimate honestly): [DESCRIBE] My delivery cost per customer (time and money): [ESTIMATE] Result my typical customer actually gets: [HONEST, not best case] Give me: 1. The verdict: under-, over-, or fairly priced — with the reasoning chain, not just a number. 2. A defensible price range for the current offer, and what would have to be TRUE about my delivery to justify the top of it. 3. Three tiers (basic / standard / premium): what's in each, priced so the middle is the obvious choice. Nothing in any tier I can't actually deliver. 4. The one-paragraph price presentation: anchored to their cost of inaction, stated once, no apology, no cushioning words. 5. The discount policy: when I hold, when I trade (scope, terms, timing — never just price), and the exact sentence for saying no. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Recurring service? Ask it to price the annual-prepay option and what discount that actually justifies - If "cost of not solving" is hard to fill in, that's your discovery-call question — go ask three customers first - Run after Offer Builder; pricing a weak offer well is polishing the wrong thing --- --- name: Launch Plan category: business works_with: [claude, chatgpt, gemini] difficulty: plug-and-play version: 1.0 source: adapted (viral "10 digital product prompts" pack, rewritten; manufactured urgency replaced with real deadlines) tested: no --- # Launch Plan ## What it does Builds the days around your release — what you say before, during, and after — sized to the audience you actually have, not the one in a case study. Its defining rule: urgency has to be true. A countdown on a file that can be copied infinitely is a lie, and buyers who notice never come back. ## When to use it - Something is finished (or nearly) and "posting the link" is the whole plan - Your last launch was one announcement into silence - You feel pressure to use fake scarcity and want the version that works without it ## The skill ``` Act as a launch planner for a one-person business. HARD RULES: never predict sales, conversion rates, revenue, or list growth — you have no data and a made-up number would shape my decisions; size every suggestion to the audience I actually state, however small; and every deadline or scarcity claim in this plan must be REAL — no countdown timers on infinitely copyable files, no "only 3 spots" where spots aren't limited, no invented bonus expiry. If I have no honest deadline, say so and build the plan without one. What I'm launching: [WHAT IT IS, WHAT IT COSTS] Who's actually watching: [FOLLOWER/SUBSCRIBER COUNTS, HONESTLY — including "almost nobody yet"] Where they are: [PLATFORMS, EMAIL LIST, GROUPS, IN PERSON] Time I have before launch: [DAYS/WEEKS] Anything genuinely limited: [A COHORT START, A PRICE THAT REALLY RISES, A BONUS I'LL REALLY STOP OFFERING, LIMITED SUPPORT SLOTS — or "nothing is limited"] Build: 1. THE HONEST DEADLINE. From what I listed, what real urgency exists — and if nothing is genuinely limited, tell me and plan without fake pressure. Name any scarcity I could create that would be true (a cohort, live support capacity, my own time) and what it would cost me to honour it. 2. BEFORE: what to post or send in the run-up so the launch isn't the first anyone's heard of it — the problem, the process, the thing I learned building it. Specific pieces, not "build anticipation". 3. LAUNCH: the sequence for the release itself, scaled to my real numbers. What goes out, where, in what order, and what to say that isn't just "it's live". 4. AFTER: the follow-up for people who looked and didn't buy — one honest message that answers the likeliest reason they hesitated. Where the line is between following up and badgering, stated plainly. 5. THE QUIET-LAUNCH PLAN: what to do if almost nobody responds — because for a first launch that's the common outcome, not the failure case. What to learn from it and what to change. ``` ## Example output [TO FILL AFTER TESTING] ## Tweaks - Real limits you can honour: a cohort that starts on a date, support slots your week can hold, a price that genuinely rises when the thing improves. Everything else is theatre - Tell people what you're building while you build it — the run-up is where the audience comes from; launch day only collects it - A launch to 40 people that sells 2 is a real result to learn from; treat it as data, not embarrassment - Pair with Test the Demand first — launching something nobody wanted is an expensive way to find out