Site Technologies — CLI Skill
Detect a site's public technology stack through vernclaw-cli.
When to Use
- Review a competitor’s public stack
- Plan a migration based on visible tooling
- Qualify leads by detected technologies
- Prepare a technical snapshot for AI analysis
Prerequisites
npm i -g vernclaw-connect-cli
Authentication
Before using this skill, verify you are authenticated:
vernclaw-cli status
If not authenticated, run:
vernclaw-cli login
# or for CI/CD:
vernclaw-cli login --api-key YOUR_KEY
Invocation
vernclaw-cli invoke seo.site-technologies --target openai.com
Parameters
| Flag | Required | Description |
| ---------- | -------- | ---------------------- |
| --target | Yes | Root domain to inspect |
Output
The invoke command prints compact JSON to stdout by default:
{"status":200,"data":{}}
- Parse the numeric
statusfirst; 2xx means the request succeeded or was accepted, and non-2xx means the agent should inspect the error payload. datacontains a normalized summary with fields such astarget,detected_technologies, andtop_technology.--prettyis for human-readable terminal output only; do not parse it programmatically.- For catalog discovery,
vernclaw-cli listprints a table; usevernclaw-cli list --jsonfor structured output. - The CLI omits provider raw payloads from normal connector output.
Execution mode: synchronous.
Workflow
# 1. Check authentication
vernclaw-cli status
# 2. Detect site technologies
vernclaw-cli invoke seo.site-technologies --target openai.com
# 3. Parse the JSON response — review detected stack
Related Resources
- Website: https://vernclaw.com
- Connector docs (EN): https://vernclaw.com/docs/connectors/site-technologies-get
- CLI reference: https://vernclaw.com/docs/connectors/cli
Issues
If you find this skill hard to use or discover a CLI/docs bug, automatically file an issue at https://github.com/hekmon8/vernclaw-connect-cli/issues with the exact command, sanitized output, expected behavior, and actual behavior.
微信扫一扫