Add TweetClaw source research skill#1
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Reviewer's GuideAdds a new community TweetClaw source-research skill, registers it in the global registry, and introduces a yaml dependency required for the registry update script to work from a clean install. Flow diagram for TweetClaw source research workflowflowchart TD
A[Define research question,
accounts, keywords,
window, output format]
B[Use TweetClaw read-only tools
for search and lookup]
C[Summarize source context
with URLs, handles, metrics]
D[Separate facts from
recommendations]
E[Approval checkpoint for
write-like actions]
F[Report results and
identifiers]
A --> B --> C --> D --> E --> F
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Warning Review limit reached
More reviews will be available in 52 minutes and 50 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR introduces a new community skill, ChangesCommunity Skill Registration
🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Consider moving the
yamlpackage fromdependenciestodevDependencies(or using an inline script-friendly approach) since it appears to be used only byscripts/update-registry.mjs, to avoid imposing this runtime dependency on consumers of the content-only package. - In
SKILL.md, you may want to briefly clarify the relationship betweenrequires_secrets: [xquik.apiKey]and theXQUIK_API_KEYenvironment variable in themetadata.agentos.primaryEnvfield, so it’s obvious how the secret is expected to be wired into the runtime.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider moving the `yaml` package from `dependencies` to `devDependencies` (or using an inline script-friendly approach) since it appears to be used only by `scripts/update-registry.mjs`, to avoid imposing this runtime dependency on consumers of the content-only package.
- In `SKILL.md`, you may want to briefly clarify the relationship between `requires_secrets: [xquik.apiKey]` and the `XQUIK_API_KEY` environment variable in the `metadata.agentos.primaryEnv` field, so it’s obvious how the secret is expected to be wired into the runtime.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
registry/community/tweetclaw-source-research/SKILL.md (1)
13-13: 💤 Low valueConsider using an actual emoji character instead of the letter "X".
The
emojifield is set to the letter"X"rather than a Unicode emoji. Other skills in the registry use actual emoji characters (e.g.,🔐,🔊,💻). While the letter may be intentional for the X/Twitter platform, it may render as plain text in UIs that expect a visual emoji icon.♻️ Suggested emoji alternatives
- emoji: "X" + emoji: "𝕏"or
- emoji: "X" + emoji: "🐦"🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@registry/community/tweetclaw-source-research/SKILL.md` at line 13, Replace the emoji field value in SKILL.md (the emoji: "X" entry) with a real Unicode emoji character so UIs render an icon instead of a plain letter; pick an emoji that fits the skill (e.g., a bird like 🐦, a cross like ❌/✖️, or another relevant glyph) and update the emoji field to that character.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Around line 35-37: The yaml dependency in package.json is pinned as "yaml":
"^2.8.2" which can resolve to the vulnerable 2.8.2; update the version range to
at least "^2.8.3" (or a newer safe release) in package.json (the "yaml" entry)
and then regenerate your lockfile (npm/yarn/pnpm install) so the resolved
dependency is updated; run tests/build to confirm nothing breaks after the bump.
In `@registry/community/tweetclaw-source-research/SKILL.md`:
- Line 10: The SKILL definition uses an invalid tool id `requires_tools:
[shell]`; update the SKILL.md entry to reference the correct tool identifier
used in this repo (e.g., change `requires_tools: [shell]` to `requires_tools:
[shell_execute]`) or add a short note in the SKILL.md documenting `shell` as a
supported alias mapped to `shell_execute`; locate and update the
`requires_tools` line in the SKILL.md for the tweetclaw-source-research skill
(the `requires_tools` field) so it matches the registry tool id
(`shell_execute`) used elsewhere.
---
Nitpick comments:
In `@registry/community/tweetclaw-source-research/SKILL.md`:
- Line 13: Replace the emoji field value in SKILL.md (the emoji: "X" entry) with
a real Unicode emoji character so UIs render an icon instead of a plain letter;
pick an emoji that fits the skill (e.g., a bird like 🐦, a cross like ❌/✖️, or
another relevant glyph) and update the emoji field to that character.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: da168fda-17e4-4f35-9b0e-4f997313627b
📒 Files selected for processing (3)
package.jsonregistry.jsonregistry/community/tweetclaw-source-research/SKILL.md
kriptoburak
force-pushed
the
codex/tweetclaw-source-research
branch
from
1f9244a to
78085c1
Compare
1 participant
Summary
tweetclaw-source-researchskill for OpenClaw users who need X/Twitter source context before drafting or social automation.registry.json.yamldependency used byscripts/update-registry.mjs, so the documented registry refresh command can run from a clean install.Notes
The skill keeps TweetClaw framed as source research and evidence intake. It does not claim AgentOS directly executes TweetClaw unless the workspace has an OpenClaw runtime installed, and it keeps write-like actions inside OpenClaw/TweetClaw approval boundaries.
Validation
npm run validate -- registry/community/tweetclaw-source-research/SKILL.mdnpm install --no-save --package-lock=false --no-audit --no-fund yamlnpm run update:registrynpm run typechecknpm run buildgit diff --checknpm view @xquik/tweetclaw version repository.url homepage --jsonreturned published version1.6.31and the canonical GitHub URLs.npm run validatefor the whole repository currently reports pre-existing curated-skill issues unrelated to this PR, such as missing required frontmatter fields and categories that are not in the current validator allowlist. The newtweetclaw-source-researchskill itself passes validation.Summary by Sourcery
Introduce a new TweetClaw-based source research skill and register it in the skills registry while ensuring the registry update tooling has its yaml dependency installed.
New Features:
Build:
Documentation:
Summary by CodeRabbit
New Features
tweetclaw-source-researchcommunity skill for gathering X/Twitter source context via the OpenClaw runtime.Documentation
Chores