Skip to content

Add Xquik X research skill#3

Open
kriptoburak wants to merge 3 commits into
pinkpixel-dev:mainfrom
kriptoburak:codex/add-xquik-x-research-skill
Open

Add Xquik X research skill#3
kriptoburak wants to merge 3 commits into
pinkpixel-dev:mainfrom
kriptoburak:codex/add-xquik-x-research-skill

Conversation

@kriptoburak

@kriptoburak kriptoburak commented Jun 16, 2026

Copy link
Copy Markdown

Summary

  • Adds a standalone xquik-x-research skill for X post, profile, timeline, and trend research.
  • Points agents at the live Xquik OpenAPI schema before building request URLs.
  • Keeps the workflow read-first, bounded, and explicit about not saving API keys or raw headers.

Validation

  • npm view x-developer@2.4.16 version license repository.url
  • Node frontmatter and schema-link check
  • Git staged whitespace check
  • Staged added-line confidentiality and punctuation scan

Summary by CodeRabbit

  • New Features

    • Added "xquik-x-research" skill enabling structured research workflows through Xquik integration with built-in error handling for common API scenarios and authentication issues.
  • Documentation

    • Introduced comprehensive skill documentation outlining prerequisites, step-by-step workflow, and error-handling behaviors for API operations.

@devactivity-app

Copy link
Copy Markdown

@kriptoburak, ⭐3 XP earned, 🏆First Pull Request Pushed completed, 💪Level 1 achieved!
Contribute more to raise your XP/Level, complete challenges for extra achievements! [Sign up for personal dashboard]

icon

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@kriptoburak, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 23 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 615ba51a-6792-4137-9078-808747fe3908

📥 Commits

Reviewing files that changed from the base of the PR and between e85816a and f33cd57.

📒 Files selected for processing (1)
  • SKILLS/xquik-x-research/SKILL.md
📝 Walkthrough

Walkthrough

Adds SKILLS/xquik-x-research/SKILL.md, a new skill document defining an Xquik-based X research workflow. It specifies front-matter metadata, prerequisites (XQUIK_API_KEY, OpenAPI schema URL), a five-step workflow (scope → schema → read → normalize → report), and error-handling rules for auth, rate-limit, server, and schema-mismatch failures.

Changes

xquik-x-research Skill Definition

Layer / File(s) Summary
Skill metadata and prerequisites
SKILLS/xquik-x-research/SKILL.md
Front-matter fields (name, description, risk, source), skill title and purpose, and prerequisites including XQUIK_API_KEY, the public OpenAPI schema URL, and an optional pinned installable package.
Five-step workflow and error handling
SKILLS/xquik-x-research/SKILL.md
Overall workflow checklist followed by per-step instructions: scope confirmation, live schema inspection, bounded read requests with route-selection heuristics, evidence normalization with sensitive-data prohibitions, findings reporting rules, and explicit error-handling mappings for missing key, 401/402, 429 (with retry), 5xx (with bounded backoff), and schema mismatches.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 Hoppin' through the tweetin' weeds,
A skill doc planted like new seeds.
Five steps to search, normalize, report —
Schema first, then auth of sort!
No raw keys stored, no leaky lines,
The rabbit approves these research designs. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add Xquik X research skill' directly and clearly describes the main change: adding a new skill for researching X content using Xquik, which aligns with the primary changeset of adding SKILLS/xquik-x-research/SKILL.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new skill documentation file (SKILL.md) for xquik-x-research, detailing prerequisites, workflow steps, and error handling for searching X posts, profiles, timelines, and trends. The review feedback suggests improving the robustness of the example curl command by using curl -G and --data-urlencode to properly handle URL encoding of search queries.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread SKILLS/xquik-x-research/SKILL.md Outdated
Comment on lines +58 to +59
BASE_URL="${XQUIK_BASE_URL:-https://xquik.com}"
curl -sS "$BASE_URL/api/v1/x/tweets/search?q=QUERY&limit=25" -H "x-api-key: $XQUIK_API_KEY"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using a raw query parameter like ?q=QUERY in a curl command can fail or behave unexpectedly if the query contains spaces, ampersands, or other special characters that require URL encoding.

To make the command robust and copy-pasteable, define a QUERY variable and use curl -G with --data-urlencode to automatically handle URL encoding.

Suggested change
BASE_URL="${XQUIK_BASE_URL:-https://xquik.com}"
curl -sS "$BASE_URL/api/v1/x/tweets/search?q=QUERY&limit=25" -H "x-api-key: $XQUIK_API_KEY"
BASE_URL="${XQUIK_BASE_URL:-https://xquik.com}"
QUERY="your search term"
curl -sS -G "$BASE_URL/api/v1/x/tweets/search" \
--data-urlencode "q=${QUERY}" \
-d "limit=25" \
-H "x-api-key: $XQUIK_API_KEY"

@kriptoburak

Copy link
Copy Markdown
Author

Addressed the query-encoding review in a66648b by URL-encoding XQUIK_QUERY before constructing the example search URL.

Validation:

  • Node URL-encoding guard check
  • Git staged whitespace check
  • Staged added-line confidentiality and punctuation scan

@devactivity-app

Copy link
Copy Markdown

@kriptoburak, ⭐3 XP earned, 🏆First Comment Added completed, 💪Level 1 achieved!
Contribute more to raise your XP/Level, complete challenges for extra achievements! [Sign up for personal dashboard]

icon

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 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 `@SKILLS/xquik-x-research/SKILL.md`:
- Around line 55-60: The curl example in the bash code block hard-codes the API
path and uses a literal QUERY placeholder, which contradicts the prose
instruction to use the exact path from the schema and makes the snippet prone to
becoming outdated. Replace the hard-coded route path and the literal QUERY
placeholder with schema-driven references that make it clear these values should
be obtained from the actual schema definition, ensuring the example stays
synchronized with the live schema rather than requiring manual updates.
🪄 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

Run ID: 290ad32a-8354-4b36-8ce5-d7a8f33510c2

📥 Commits

Reviewing files that changed from the base of the PR and between ee0548d and e85816a.

📒 Files selected for processing (1)
  • SKILLS/xquik-x-research/SKILL.md

Comment thread SKILLS/xquik-x-research/SKILL.md
@kriptoburak

Copy link
Copy Markdown
Author

Addressed the schema-driven example review in f33cd57:

  • Replaced the hard-coded request path with XQUIK_PATH from the OpenAPI schema.
  • Replaced the literal query parameter with XQUIK_QUERY_PARAM from the schema.
  • Kept the research topic value URL-encoded before the request.

Validation:

  • Node guard check for schema-driven placeholders
  • Git staged whitespace check
  • Staged added-line confidentiality and punctuation scan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant