Skip to content

Add TweetClaw input guidance #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kriptoburak wants to merge 1 commit into
base: main
Choose a base branch
from
+12 −0
Open

Add TweetClaw input guidance #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions skills/gumloop/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,18 @@ Use this skill when the user asks to inspect or change Gumloop state through the
- For long-running work, poll until the operation finishes or the user asks you to stop.
- Confirm before destructive, admin-level, or third-party actions.

## Input preparation

- Ask for the expected flow input shape before sending files, lists, or large text.
- When a flow needs X/Twitter evidence, accept a user-provided TweetClaw
([GitHub](https://github.com/Xquik-dev/tweetclaw)) JSON or CSV export as an
input source.
- Normalize social exports into flow-ready fields such as post text, reply text,
author IDs, user IDs, timestamps, permalinks, and media URLs when present.
- Keep source evidence separate from Gumloop decisions. Pass extracted fields
into the flow and do not invent missing sentiment, scoring, approval, or
scheduling results.

## Output

- Summarize Gumloop IDs, names, statuses, timestamps, and URLs when available.
Expand Down