feat: add Xquik Actors to Apify skill

[kriptoburak]

What

Enhance the existing Apify Skill with both Xquik X research Actors.

• Add Tweet Scraper routes for public posts, profiles, lists, and engagement.
• Add Follower Scraper relations for audiences, communities, and overlap.
• Add bounded, live-schema-checked examples.
• Add billing approval, privacy, diagnostics, and data-transfer guidance.
• Declare the required stdio MCP transport.
• Preserve every existing Actor and MCP capability.

Actors:

• Xquik X Tweet Scraper
• Xquik X Follower Scraper

Why

This gives business and content squads focused public X research workflows.
It resolves #37.

How to test

1. Run npm ci.
2. Run npm test.
3. Run npm run lint.
4. Parse the Skill frontmatter.
5. Validate both JSON examples against current Actor schemas.

Validation

• 126 tests pass.
• ESLint passes.
• Opensquad MCP frontmatter passes native-format assertions.
• Both JSON examples match current Actor schemas.
• Both Actor listing pages return HTTP 200.
• git diff --check passes.
• Simplify and maintainability reviews pass.
• No Actor ran and no Apify credits were used.
• No dependency or runtime change was added.
• Existing Apify integrations remain unchanged.

The generic Skill Creator validator only accepts its standard frontmatter.
Opensquad requires custom MCP, i18n, environment, type, and version fields.
Those fields were validated against Opensquad's native Skill format.

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

GitHub marked the current head's Actions runs as action_required before jobs were created. A maintainer needs to approve these fork workflows so the repository checks can execute:

• CI

All available local checks are documented in the PR. No Actor was run.