Thanks for helping improve Vibe Coding Hub SEO Skills.
The v0.1.x line is intentionally limited to read-only Google Search Console, Bing Webmaster Tools, and Yandex Webmaster workflows. Keep provider CLIs independent unless a shared abstraction removes proven duplication without weakening platform-specific safety rules.
Open an issue before proposing a new provider, dependency, write operation, or credential model. Small documentation, normalization, test, and compatibility fixes can go directly to a pull request.
- Node.js 22 or 24.
- No real provider credentials or website data.
- Mock responses for every automated test.
Run the complete local gate:
npm run check
npm test- Keep changes focused on one problem.
- Add or update tests for behavior changes.
- Preserve exact property, site, and host identifiers.
- Keep aggregate totals distinct from Top-row datasets.
- Do not log credentials, raw queries, page URLs, or private metrics.
- Update the relevant
SKILL.md, reference, and changelog entry when user-facing behavior changes.
Credential storage, OAuth flows, API endpoints, repository-path checks, permission checks, redaction, and raw-output defaults are security boundaries. Changes to them require explicit tests and a clear rationale in the pull request.
Do not include real tokens even in reverted commits. If sensitive data enters Git history, rotate it immediately and follow SECURITY.md.
Use concise, imperative commit subjects. Releases follow semantic versioning; all plugin manifests and the Claude marketplace entry must carry the same version.