feat: add xquik community skill#2
Conversation
Reviewer's GuideAdds a new community skill definition for the Xquik X/Twitter data integration, including AgentOS metadata, setup guidance, usage workflows, examples, and safety constraints for using Xquik MCP and API securely. Flow diagram for using the Xquik X Data skillflowchart TD
U[User request about X/Twitter data]
A[Agent selects xquik-x-data skill]
S{API key available in secure store?}
K[Ask user to provide scoped Xquik API key]
C[Store key as XQUIK_API_KEY or equivalent]
M{Client supports MCP tools?}
MCP[Use xquikMcp for search, reads, extractions]
REST[Use xquikApi REST endpoints/webhooks]
R[Summarize results and respect constraints]
U --> A --> S
S -- No --> K --> C --> M
S -- Yes --> M
M -- Yes --> MCP --> R
M -- No --> REST --> R
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughA new community skill, ChangesXquik X-Data Skill Registry Entry
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 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 clarifying how
xquikMcpandxquikApimap to concrete tool or MCP server names (e.g., expected tool identifiers or MCP URI), so integrators know exactly what to configure. - It may be useful to explicitly state that the skill should only be used with public or appropriately consented X/Twitter data, and that the assistant should avoid attempting to access private/protected content beyond what the API legitimately exposes.
- In the constraints/setup sections, you might want to add guidance that webhook endpoints must use HTTPS and that signing secrets and callback URLs should be treated as secrets stored in the platform’s secure store, mirroring the API key handling.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider clarifying how `xquikMcp` and `xquikApi` map to concrete tool or MCP server names (e.g., expected tool identifiers or MCP URI), so integrators know exactly what to configure.
- It may be useful to explicitly state that the skill should only be used with public or appropriately consented X/Twitter data, and that the assistant should avoid attempting to access private/protected content beyond what the API legitimately exposes.
- In the constraints/setup sections, you might want to add guidance that webhook endpoints must use HTTPS and that signing secrets and callback URLs should be treated as secrets stored in the platform’s secure store, mirroring the API key handling.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: be8bddce34
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,51 @@ | |||
| --- | |||
| name: xquik-x-data | |||
There was a problem hiding this comment.
Adding this SKILL.md without also updating the generated registry.json leaves the package's exported catalog unchanged: in this commit registry.json still has skills.community: [] and communityCount: 0. Consumers that import @framers/agentos-skills or ./registry.json will not discover xquik-x-data even though the file is shipped, so please regenerate and commit the registry after adding the skill.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Addressed in 3a32b63. registry.json now includes xquik-x-data under categories.community, adds the skills.community entry, updates stats to 89 total and 1 community skill, and refreshes the registry timestamp.
Validation rerun:
npm run validate registry/community/xquik-x-data/SKILL.md- registry JSON assertion
npm run typechecknpm run buildgit diff --check
1 participant
What changed
registry/community/xquik-x-data/SKILL.md.Validation
npm run validate registry/community/xquik-x-data/SKILL.mdpassed.npm run typecheckpassed.npm run buildpassed.git diff --checkpassed.Notes
npm run validatewithout a path still fails on existing curated skills unrelated to this PR. The new community skill passes its targeted validator.Summary by Sourcery
Add a new community skill definition for working with X/Twitter data via the Xquik MCP and API.
New Features:
Documentation:
Summary by CodeRabbit
New Features
Documentation