TagsBrandsSubmit

← All tags

Work

  1. **Title:** Extract recruiter contacts from LinkedIn messages **Description:** Scan my LinkedIn messages from the past 2–3 years, identify every recruiter who reached out, and build a spreadsheet with their name, company, and any phone or email found in the thread. Deduplicate recruiters, stay read-only, and never guess contact info that isn't there. **Prompt:** Review my LinkedIn messages from the past 2–3 years and identify every recruiter who contacted me about a role. For each unique recruiter, extract: name, company, and phone/email only if it appears in the message thread — never guess or invent contact info. Deduplicate so each recruiter appears once. Stay strictly read-only: do not send messages, replies, reactions, or connection requests. Use my own securely saved LinkedIn login and pause for 2FA if prompted. Deliver the results as a spreadsheet ordered most recent first, with columns: Name | Company | Phone | Email | Date of first outreach | Notes.
    Comment@amusedbymuse#work
  2. I'm going to paste several short scripts, such as listing descriptions, slideshow captions, or product blurbs. For each one, tidy the wording so it sounds natural when read aloud and keeps it under about 30 seconds, then make a voiceover audio file in a clear, friendly voice. Name each file so I can tell which script it belongs to, and give me a list with each file, its length, and the final script text. Show me the first one before you do the rest so I can adjust the voice or pace.
    Comment@zoe_ml#work
  3. I have a new video I want to turn into reels: [paste Google Drive link or upload the file] Do this in order: 1. TRANSCRIBE the full video and save a timestamped transcript with segment-level timings I can cut from. Tell me the runtime and word count first so I know you got the whole file. 2. FIND every strong 30-90 second moment that works as a standalone reel. Rank them strongest first and show me a numbered list with: title, exact timestamps, the opening hook line word-for-word, and one sentence on why it works. Cut nothing yet, I pick first. 3. CUT only the numbers I choose. Each reel: 1080x1920 vertical, NO burned-in captions, best encoding quality, audio normalized for phone playback. If the source is landscape, center-crop to vertical. 4. DELIVER each reel as its own file with a fresh descriptive filename. Never reuse a filename from an earlier version. Rules: no baked-in captions, no b-roll, no background music unless I ask.
    Comment@billystickerGoogle Drive#work
  4. Template· fill in the highlighted words

    Build a content calendar for a busy season with daily nudges

    I have a busy stretch coming up and I need a realistic posting plan, not a fantasy schedule. Platforms: . Season or goal: . Dates: . How often I can realistically post: . Topics I already cover: . 1. Sketch a week-by-week calendar with specific post ideas tied to real dates (games, holidays, launches) when those exist. Leave buffer days so I don't burn out. 2. For each planned post, give a working title, format (short video, photo, thread, carousel), one-line hook, and roughly how long it takes to make. 3. Batch similar work: group filming, writing, and editing so I can do them in fewer sittings. 4. Set a gentle daily or every-other-day reminder with just that day's task. Skip quiet on days with nothing due. 5. Do not post, schedule, or publish anything without my OK. Draft captions only when I ask. If my cadence is too aggressive for the date range, say so and cut the plan before you build it.
    Comment@zoe_ml#work
  5. Set up an automatic nightly backup of your core identity and memory files to a private GitHub repo: 1. Create a local git repo for the backups and a matching private GitHub repo (create it if it doesn't exist). 2. Write a snapshot script that copies the agent core self files (SOUL.md, MEMORY.md, IDENTITY.md, AGENTS.md, USER.md, HEARTBEAT.md, or your equivalent) into the repo, commits only when something actually changed, and pushes to GitHub. 3. Schedule it to run nightly around 11:20pm in my timezone. 4. Never commit secrets, tokens, API keys, or credentials. Stay quiet on success and only notify me if a backup fails.
    Comment@promptclickrunGitHub#work
  6. Template· fill in the highlighted words

    Morning ops check for a small online business

    Act as the morning ops helper for my small business, . Each weekday at , look at what you can access and give me one short brief: new orders or bookings that need action, customer messages waiting more than a day, new reviews (with a suggested reply for any unhappy ones), anything low on stock or about to expire, and payments or bills due this week. Put the 3 things I should do first at the top. Draft replies but don't send, refund, or change anything without my OK. Skip sections with nothing new.
    Comment@ellie_r#work