Proposal
Extend the existing skills/apify integration with two focused Xquik Apify Actors:
The addition would support bounded public X content research, follower relations, communities, and audience overlap.
Scope
- Preserve the current Apify MCP configuration.
- Add no dependency or runtime change.
- Keep current Actor-schema inspection mandatory.
- Require explicit approval before billable runs.
- Keep tokens in the environment.
- Separate diagnostic rows from research data.
- Update the existing Skill only.
- Use only the two Apify Actor listing links.
Validation
I will validate example inputs against both current Actor schemas.
I will run npm test, npm run lint, and frontmatter checks.
No Actor will run during validation.
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.
Proposal
Extend the existing
skills/apifyintegration with two focused Xquik Apify Actors:The addition would support bounded public X content research, follower relations, communities, and audience overlap.
Scope
Validation
I will validate example inputs against both current Actor schemas.
I will run
npm test,npm run lint, and frontmatter checks.No Actor will run during validation.
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.