Automation & Ops sitemap-authoringbrowser-automationopencliagent-guidanceknowledge-management

OpenCLI Sitemap Author

Create and maintain site task graphs for browser agents to navigate effectively.

FollowSkills review · FSRS-2.0
Not recommended
56/ 100 5-point scale 2.8 / 5
1 2 3 4 5 6
1Trust16 / 25 · 3.2/5

Evidence shows the skill explicitly prohibits writing secrets, cookies, user-private IDs, and bypassing CAPTCHA/access controls, emphasizing browser state as truth, demonstrating good security awareness and least privilege. However, allowed-tools include Bash(opencli:*), potentially accessing system commands, but the skill mainly guides sitemap file operations without explicit data-flow or user confirmation. Deduction: no explicit user confirmation step, unclear data flow, no rollback mechanism.

2Reliability8 / 20 · 2.0/5

The skill provides detailed schema and examples with good self-consistency. However, static review cannot verify execution, and it depends on external opencli tool, browser state, and network, with no tests or error-handling details provided. Deduction: happy path only in docs, abnormal input behavior unclear, external dependencies.

3Adaptability9 / 15 · 3.0/5

The skill explicitly describes use cases (create/maintain sitemaps), target users (AI agents), and environment requirements (opencli browser), with size heuristics and advice. However, non-fit scenarios are not clarified, trigger conditions depend on 'opencli browser' environment, and reachability in mainland China is not verified. Deduction: boundaries and triggers insufficient, environment fit evidence lacking.

4Convention11 / 15 · 3.7/5

SKILL.md provides clear structure, storage model, schema, and examples, documents v1.1 changelog, follows Apache-2.0 license, maintenance responsibility traceable to repo. But no version number, changelog file, or explicit update mechanism. Deduction: version management and update path unclear.

5Effectiveness7 / 15 · 2.3/5

The skill has clear goals and detailed sitemap authoring specs, producing structured sitemap files directly usable. But its value depends on external opencli tool, and static review cannot verify actual output. Deduction: correctness unverified, cost-benefit not quantified.

6Verifiability5 / 10 · 2.5/5

Document mentions multiple PoC validations (twitter, hackernews) and Phase 2 audit plans, but static review lacks executable test evidence. Deduction: no third-party execution evidence, fact/inference separation incomplete.

Evidence confidence:Low Reviewed Aug 07, 2026 Reviewed revision 399c0de2a76e
The upstream repository has new commits since this review. The score still applies to the reviewed revision shown and may not cover the latest changes.
Before you use it
  • This skill depends on opencli browser and browser state; static review cannot verify its actual runtime behavior. Use with caution in real environments.
  • The skill involves operating on websites; ensure compliance with site terms of service and laws.
  • The skill lacks explicit user confirmation mechanisms; consider adding user authorization confirmation in practice.
  • Reachability in mainland China is unverified; all features may rely on overseas services.
See the full review method →

What does this skill do, and when should you use it?

The OpenCLI sitemap-author skill enables AI agents to create and maintain site sitemaps that are not for SEO but as navigation and execution graphs for agents. It documents page-state signatures, action edges, workflows, and pitfalls so agents can decide where they are, what path to take next, and how to recover. The skill emphasizes small, verifiable sitemaps, prioritizes local overlays, and ensures agents follow user-provided instructions.

Reads existing local and global site sitemaps, verifies current browser state using opencli browser commands (state, find, network, analyze), writes or updates sitemap files under ~/.opencli/sites/<site>/sitemap/ based on observed stable structures, records action edges with required schema and recovery directives, and marks stale items when browser state conflicts.

  1. After exploring a site, wanting to record the stable workflow you discovered for future agents to reuse.
  2. Updating sitemap entries when the existing sitemap is stale and disagrees with current browser behavior.
  3. Promoting local site knowledge into the repo sitemap when agents need structured guidance beyond blind clicking.
  4. Maintaining sitemaps for frequently used sites, focusing on task-relevant paths and stable anchors.
  5. Creating partial pages for cross-page UI components like shared card components.

What are this skill's strengths and limitations?

Pros
  • Emphasizes small, verifiable sitemaps, avoiding crawling the whole site.
  • Provides a clear authoring loop and verification requirements.
  • Supports local overlays and global promotion, allowing safe iteration.
  • Includes partial pages for cross-page UI elements.
  • Explicitly marks uncovered routes to manage agent expectations.
Limitations
  • Requires OpenCLI setup and browser bridge extension, which could be a barrier to adoption.
  • Primarily for advanced users; the schema may have a steep learning curve.
  • No documented test suite; verification relies on manual inspection.
  • Effectiveness depends on the maintainer's discipline to keep sitemaps small and accurate.

How do you install this skill?

Install the OpenCLI collection: npx skills add jackwener/opencli --skill opencli-sitemap-author. Requires the OpenCLI runtime and Browser Bridge extension; follow the Quick Start steps in the README.

How do you use this skill?

Trigger with a prompt like: "Record the stable workflow you just discovered for this site" or "Update the sitemap for this site, emphasizing current state." The skill automatically reads existing memory, verifies browser state, and guides you through writing or modifying sitemap files.

FAQ

How is this skill different from an SEO sitemap?
This skill creates an agent-facing execution graph, not an SEO sitemap for search engines; it records actions, state signatures, and recovery paths.
Do I need special software installed?
Yes, you need the OpenCLI runtime and Browser Bridge extension, along with the `opencli browser` command available.
Where are sitemaps written?
Primarily in `~/.opencli/sites/<site>/sitemap/`, with optional promotion to the global sitemap directory for review.
What if the sitemap conflicts with the live site?
The skill trusts the current browser state and marks conflicting items as stale rather than forcing the old path.

More skills from this repository

All from jackwener/OpenCLI

Related skills