opencli-browser-sitemap
Technical SEOjackwener/opencliskills.sh ↗
Installs
5,870
deduplicated, at the last sync
Since we started
+2.8%
39 readings, about 2 hours apart. Not a live curve.
Our category
Technical SEO
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill guides an agent's interaction with a website using opencli browser by consuming site sitemap files when available. It helps reduce blind navigation by providing structured context, but it emphasizes that the live browser state must always take precedence over the sitemap information. The skill provides methods for updating local knowledge about adapter health and marking stale sitemap entries.
- Path chosen: adapter best path or browser fallback
- Checkpoint reached: current URL/state signature
- Sitemap health: used as-is, stale marked, or missing workflow
- opencli browser open or analyze report
- site sitemap files (SITE.md, pages/*.md, workflows/*.md)
not detected
The evidence does not contain any information regarding paid services.
not detected
The evidence does not contain any information regarding registration requirements.
It cannot override the live browser state if it conflicts with sitemap data. It requires specific opencli commands and file structures to function correctly, such as reading local overlay or global seed files. It is limited to providing context for navigation rather than executing arbitrary code outside of defined paths.
Evidenceskills/opencli-browser-sitemap/SKILL.md:1-97
--- name: opencli-browser-sitemap description: Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live browser state. allowed-tools: Bash(opencli:*), Read, Edit, Write, Grep --- # opencli-browser-sitemap Use this skill when `opencli browser open` or `opencli browser analyze` reports `sitemap.available: true`, or when the user asks you to use a site's sitemap. The sitemap is **prior knowledge**, not ground truth. It should reduce blind clicking, but it must never override the live browser state. --- ## Consumption Loop 1. Run or reuse `opencli browser <session> state` to know the current page. 2. Read only the smallest relevant sitemap files: - `SITE.md` for site-level orientation. - One matching `pages/<page-id>.md` for current state. - One matching `workflows/<task-id>.md` for the user goal. - `pitfalls.md` only when blocked or warned by the workflow. 3. Prefer the workflow's **Best path**. If it names an adap
Read 1 of 1 text files in the skill.
Installfrom the directory
npx skills add https://github.com/jackwener/opencliInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
1 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 5.7k, not zero — the range is 5.7k to 5.9k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
You must trust reality and follow the visible page state. You should re-run `state` or `find` with semantic anchors, check for differences in login or locale, and mark the sitemap item as stale.
The provided documentation does not mention any requirements for paid services.