agentleFS
matthewdonsemail-labmatthewdonsemail-lab/log/.claude/skills/log-facebook-groups/SKILL.md

log-facebook-groups

Skill63 starsChanged yesterdayMITView on GitHub

Listening to local Facebook groups. A log play (docs/useCases/facebook/groups.md): The same accounts can join the local groups in their town and hear when someone asks for what the business sells (\"anyone know someone who can take away an old sofa?\"). This page shows the parts.

The file

Files
SKILL.md

Listening to local Facebook groups

This is the log play facebook/groups. Before anything else, call the log MCP tool getGuide({ useCase: "facebook/groups" }): it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order.

Draft every message from that person's own thread and matt's real replies (voice with no text, search), never from memory, and never send two that read alike (sameAsSent).

The same accounts can join the local groups in their town and hear when someone asks for what the business sells ("anyone know someone who can take away an old sofa?"). This page shows the parts.

flowchart LR
  join["1. join the group<br/>log facebook join group"] --> poll["2. poll it every 5 min<br/>log facebook poll"]
  poll --> magpie["3. OpenMagpie keeps every post<br/>and picks the matches"]
  magpie --> twenty["4. matches land in<br/>Twenty socialListening"]

How the owner asks for it: "join the local facebook groups in <town>", "listen to the facebook groups for people asking for <service>", "read the posts in the facebook group", "poll the facebook group for new posts", "find the business owners in the facebook group".

How it runs

An account asks to join a neighbourhood group in its town. Once in, each poll brings back the group's newest posts as a step in the account's open browser, nothing clicked and no comments opened. A read by hand (read group) can add their comments; without --live, on a numeric group id, it runs on the direct-API engine (fbk) first when the account has a saved session, and falls back to the open browser. What each part must do is in the spec, Facebook groups.

The commands

#StepMCP toolWhat decides itCommand
1JoinfacebookJoinGroup, facebookJoinGroupLivethe group's own join statelog facebook join group --account <a> --group <url or id> [--live]
2ReadfacebookReadGroupthe feed's answer; the direct API first, the browser behind itlog facebook read group --account <a> --group <id>
3PollfacebookPolleach read's answer; OpenMagpie's watch picks the matcheslog facebook poll <group> <account> <how long>
4MembersfacebookReadMembersthe members list's answers, about 10 more per scrolllog facebook read members --account <a> --group <g> --count 40 --owners

read members --owners keeps people whose bio says owner, founder, CEO or self-employed, or who run a page, saved under ~/.logCli/members/.

Next

  • #40 acts on a match: a comment or a message from the same account.

Sources: docs/groupListening.md, docs/groupMembers.md, docs/commandNaming.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.