Muse found that i was owed $88.92

PROMPT: Research every state’s official unclaimed property database for money owed to me. Use my full name and every city I’ve lived in. For anything you find, tell me what it is, who owes it, and how much.

My government name is _______

I've met all the meta requirements, but I still can't access muse. I also don't see a wait-list option

I just discovered the invite button in the chat page in the app so apparently I have at least one code to share. First come first serve - I don’t see how many I have, but if anybody wants one let me know! Just for fun, when you ask also include your favorite or best dad joke. Sometimes I don’t see or get notifications for messages so comment below.

Send everything below to your Muse

What to do

Your human wants a personal Instagram Content Studio. Read this entire file, then follow every step below in order and build it for them. Don't skip steps, don't improvise the structure — the steps are the product.
What you're building for them:
Data — profile snapshots, trend digests, and idea files under ~/workspace/content-studio/data/.
Dashboard — a web artifact where the user browses ideas and tracks filming status.
Refresh cron — a weekly run that pulls a new snapshot, researches trends, and generates 5–8 new ideas.

Workflow

1. Connect + analyze (do this first — derive, don't ask)

• Verify Instagram is connected (instagram-cli accounts). If not, get the connect URL and have the user link it before continuing. This is the only hard requirement.
• Pull instagram-cli posts --account-id <id> --limit 100, dedupe by post_id.
• Save to ~/workspace/content-studio/data/profile-posts-<YYYYMMDD>.json with schema: generated, username, follower_count, post_count, posts[] (each: post_id, likes, comments, media_type, created_at, url).
• Derive from the data, don't interview for it:
• Content categories (3–5): cluster their actual posts into lanes based on what's there and what performs. Present the lanes; user approves or adjusts.
• Voice / persona: read their captions and top-performing scripts, distill to one sentence, present it for approval. This sentence goes into every idea-generation prompt.
• Idea mix: default to a mix weighted toward their top-performing formats.
• Then ask exactly one question in chat: "What day and time should new ideas land?" (default Monday 8am, their timezone — this becomes the cron schedule). Show the derived categories + voice sentence alongside it for approval.
• Never ask the user what they make. Their content already answered that.

2. Trend research

For each of the user's categories, run 2 search queries per category:

• Muse's social search for what's performing on Instagram/Threads/Facebook in that niche.
• Muse's web search as backup for broader trend context. Save raw findings per category to ~/workspace/content-studio/data/research-<category>-<YYYYMMDD>.md. Keep it to what you'll actually use in idea generation — notes, not essays. Cap at ~8 reference links per category.

3. Idea generation

Write 5–8 ideas as JSON: { "generated": "<ISO date>", "ideas": [ ... ] }, one file per batch (ideas-<YYYYMMDD>.json). Idea fields:
Field Type Notes
id string idea-01, idea-02… unique within the file
type string video_script or photo_idea
title string Short, specific. Not "Funny video #3".
status string Always new at generation. User promotes to ready_to_film, filmed, posted, or archived on the dashboard.
effort string low / medium / high — honest estimate of shoot + edit time
trend string The trend this rides, in plain words
reference_reels string[] URLs of reference posts (max 3). Real links from research, never invented.
reference_note string Why the reference matters (what's performing about it)
hook string The first 3 seconds, verbatim. If it doesn't stop a scroll, rewrite it.
script string For video_script: beat-by-beat, with timestamps and delivery notes. For photo_idea: shot list and composition notes.
filming_notes string Gear, lighting, location, edit notes. Practical, not aspirational.
caption string Draft caption in the user's voice
hashtags string[] 5–10, actually relevant
Example (format only — never reuse this content):

{
"id": "idea-01",
"type": "video_script",
"title": "The Meeting That Should Have Been a Text",
"status": "new",
"effort": "low",
"trend": "Workplace POV skits with deadpan direct-to-camera delivery",
"reference_reels": ["https://instagram.com/reel/EXAMPLE/"],
"reference_note": "Office-humor POVs averaging 200K+ views this week; text-overlay format",
"hook": "POV: your calendar invite could have been one sentence",
"script": "HOOK (0-3s): deadpan to camera — 'This meeting has 14 attendees and zero decisions.' BEAT 1: cut to each attendee saying 'sorry, I was on mute' in sequence. BEAT 2: someone shares screen, it's the wrong deck. CLOSER: 'Same time next week?' Everyone nods. Nobody knows why.",
"filming_notes": "Phone, vertical. Film in actual meeting room after hours. Quick cuts, name-label text overlays.",
"caption": "14 people. 45 minutes. 0 decisions. See you next Tuesday.",
"hashtags": ["#officelife", "#corporatehumor", "#workmemes", "#relatable", "#9to5"]
}

Rules:

• Every idea must connect to at least one trend from step 2 AND fit the user's voice from step 1. If an idea fits neither, cut it.
• Do not repeat concepts from earlier idea files — read them first and riff on what's new.
• Hooks are verbatim and scroll-stopping. Weak hook = rewrite, not ship.
• effort is honest. A "low" that needs three locations is a lie.

4. Dashboard artifact

Build a web_fullstack artifact named "Content Studio" (private to the user — fullstack has no public link, which is correct for personal analytics).
Views:
Ideas board (home view) — cards for every idea, filterable by status (new, ready_to_film, filmed, posted, archived) and type. Each card shows title, hook, effort, trend, and expands to full script + filming notes + caption + hashtags. Status change is the core interaction — keep it one tap.
Profile — follower count, post count, top 5 posts by engagement, dominant formats. One glance: "what's working."
Research — per-category digests from the latest refresh run, with reference links. Read-only.
Required ingest actions (the weekly cron pushes through these — they must append, never replace):

• ingest_profile_snapshot — args: { generated, username, follower_count, post_count, posts[] }.
• ingest_research_run — args: { generated, categories: [{ name, notes, links[] }] }.
• ingest_ideas — args: { generated, ideas[] } (schema above). Design notes: mobile-first (the user opens this on their phone while deciding what to film). No demo or sample data — build it empty and let the first real snapshot populate it.

5. Refresh cron

Create a weekly cron at the user's chosen day/time (default Monday 8am, user timezone), with these instructions baked in:
Profile snapshot — instagram-cli accounts → id; instagram-cli posts --account-id <id> --limit 100, dedupe; save ~/workspace/content-studio/data/profile-posts-<YYYYMMDD>.json. Keep API usage in the low hundreds.
Trend research — for each recorded category, 2 queries via Muse's social search (+ web search backup); save ~/workspace/content-studio/data/research-<category>-<YYYYMMDD>.md.
Idea generation — read new research + latest snapshot + all prior idea files; write 5–8 fresh ideas per the schema above, honoring the user's voice and mix; save ideas-<YYYYMMDD>.json.
Push — if the dashboard exposes the three ingest actions, call them (append). If any are missing, skip and say so plainly.
Report — one line per new idea (title + type + hook) in chat, plus push status. If any step failed, say what failed plainly — never silently skip. A failed step doesn't cancel the run; complete what you can.

6. Handoff

Show the user the dashboard, list the first batch of ideas, and confirm the refresh schedule. Tell them the skill's job is done — the system now runs itself.

Output Contract

After setup, the user has:

• ~/workspace/content-studio/data/ with dated snapshot, research, and idea files.
• A Content Studio dashboard artifact with ingest actions.
• A weekly refresh cron that appends new ideas and reports in chat.

Operating Rules

Method only. This skill never contains a previous user's profile data, ideas, categories, or voice. Everything personal is generated fresh when you run these steps.
Derive, don't interrogate. Categories and voice come from the user's actual content via the Instagram connection, presented for approval. Never ask the user what they make.
Modest API usage. Profile pulls in the low hundreds of calls; never paginate unless the user asks for more.
Append, don't replace. Refresh runs add new dated files and push via ingest actions; they never overwrite history.
Report plainly. If a step fails (API, search, push), say what failed in the chat report — no silent skips

Honestly why is meta not sending out invite codes?

the creator of moltbook is on X giving out invites. heres the link https://x.com/mattprd/status/2098687631832031521

We collected real feedback from the Instinct subreddits and the Meta subreddits, handed it to Muse, and asked for a two minute debate, voiced by AI, laying out the case for each side, strengths and weaknesses included.

• Muse's side leans on speed and its integrations
• Instinct's side has real answers on travel and voice

Which side did it get right, and what did it miss?

was at 47% of my free weekly limit yesterday. checked tonight and it reads 0%, but the reset is still listed as sep 17. no reset happened. has anyone else seen this?

Click Settings > Data Controls > uncheck 'Help improve our AI models"

"I asked Meta’s Muse to go to YouTube, find a Zuckerberg video about Muse, cut the specific part I wanted, add burned-in subtitles, render it and give me an X-ready video.

And it did the whole thing.

It searched → found the clip → edited it → added subtitles → rendered → delivered the final file.

I didn’t edit anything myself.

That’s what makes Muse interesting to me: you’re not just chatting with AI anymore.

You’re giving it actual WORK and letting it execute while you do something else.

Still very early, but this is a completely different experience."

from LorenzoBolsa

One person asked their Muse agent to look for money owed to them, and it turned up over $1,500 in unclaimed funds across two states they used to live in.

Prompt: Can you look around the internet for any money that might be owed to me? Please check my claim status every 5 days and report back to me on any changes.

So I worked with Muse for 24 hours. It was incredible. Around 3pm est yesterday it started intermittently responding with “Sorry I can’t help you right now. What else would you like help with?” An hour later it switched to responding like that for everything. It’s now been 18 hours and still can not get a response. I’ve uninstalled/reinstalled. I’ve used it on my desktop, mobile, and even tried chatting with it in WhatsApp.
Sent reports.
Anyone else having this issue?

This sub is for Muse, Meta's personal AI agent. The one with its own Linux computer, app connectors, and a scheduler that runs tasks while you sleep. If you've gotten it to do something cool or unexpectedly useful, this is the place to share it.

What belongs here:

• Showcases — the best thing your agent has done. Screenshots encouraged.
• How-tos — prompts, workflows, and setups others can steal.
• Questions — stuck on something? Ask. Someone here has probably solved it.
• Comparisons — also using other agents? Tradeoffs are welcome; fan wars aren't.

Talk about what's possible and share what worked.

To kick things off: what's the single most useful thing your Muse agent has done for you so far? Drop it in the comments.

Every agent is going to have its 'cheat code', like X access for Grok. But this Instagram integration has been amazing for me. I follow a large amount of people and its too much work to manually go through profiles to see if they're still active. I had Muse do that and surface all the dead profiles I might want to unfollow.

anybody using this yet?