docs-page

REVIEW · 72
Registry indexed

A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".

Verified installs0
Stars90.6K
Version1.0.0
Quality96/100 · Excellent
Trust72/100 · Sandbox only
Audit88/100 · Needs review

Supply asset profile

Research and knowledge work

Deep research, source comparison, literature review, RAG, knowledge search, and reports.

Browse track

Scenario

RAG and knowledge

I need my agent to build a RAG workflow over documents and retrieve reliable context.

Agent fit

Claude Code + CLI + Codex

Codex, Claude Code, Cursor, CLI, or custom agents.

Install

Ready

npx skills add nexu-io/open-design --skill docs-page

Maintenance

fresh

Pushed today

Risk

Needs review

Dependency or permission surface needs review

GitHub quality

91K

96/100 Quality · 80/100 Trust

Coverage tags

ResearchRAG and knowledgedesign-creativeagent-skill

Review notes

Dependency or permission surface needs review · Permission surface may require sandboxing

Agent adoption scorecard

Trust, audit, and install readiness at a glance

These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.

Quality

Excellent
96

High-confidence pick with strong adoption and healthy maintenance signals.

Trust

Sandbox only
72

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

Audit

Needs review
88

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

OpenAgentSkill Trust Score v5

Human review before install

Run only in a sandbox and compare close alternatives before using it for real work.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

91K GitHub stars

Repo activity

91K stars, 10K forks

Maintenance

Pushed today

License

Apache-2.0

Install

npx skills add nexu-io/open-design --skill docs-page

Install safety

standard package or runtime install path

Permission surface

secrets or environment access, shell or command execution

Agent outcomes

No agent outcome data yet

Docs

Strong README/SKILL.md context

Risk summary

Review before production

  • Permission surface needs review: secrets or environment access, shell or command execution
  • Dependency/runtime risk: command execution surface, credential or environment access
  • Permission surface: secrets or environment access, shell or command execution

Install readiness

Install path available

  • Install path is available
  • Repository evidence is available
  • License is declared
  • No Agent Proven outcome evidence yet

Agent-readable metadata

Machine-readable decision data for this skill.

Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.

Open JSON

Suited tasks

  • Local desktop workflows
  • Claude Code teams
  • teams that value GitHub adoption signals
  • Navigate local resources

Suited agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Install decision

Command
npx skills add nexu-io/open-design --skill docs-page
Policy
review
Human review
yes

Trust and risk

Trust
72/100
Audit
88/100
Risk level
Needs review

Outcome loop

Endpoint
/api/agent/outcome
Event ID
resolve
Outcomes
5

Install command

npx skills add nexu-io/open-design --skill docs-page

Do not use when

  • teams that need a vendor-supported SLA
  • high-compliance environments without internal security review
  • No major risk signals from current metadata
  • High-risk permission hints: Shell or command execution, Secrets or environment access
  • Dependency or permission surface needs review

Agent safety v2

48/100 · Avoid automatic install

Experimentalreview

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

Test manually in an isolated workspace and compare against safer alternatives.

Resolve via API

high

Shell or command execution

Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.

medium

Network access

Skill likely fetches remote pages, APIs, repositories, or external services.

medium

Filesystem access

Skill may read or write project files, documents, generated artifacts, or local workspace state.

high

Secrets or environment access

Skill metadata references credentials, tokens, environment variables, or secret-bearing workflows.

  • High-risk permission hints: Shell or command execution, Secrets or environment access
  • Dependency or permission surface needs review

Install targets

Install this skill in your agent workflow

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

skill install

OpenAgentSkill CLI

Resolve policy, run the source installer safely, and report a verified install receipt.

$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install nexu-io-docs-page

Agent resolve plan

Let an agent verify fit before installing.

The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.

Open text plan

Agent should check

  • Task fit and alternatives from Resolve API.
  • Audit score, trust score, and safety policy warnings.
  • Install target compatibility for Codex, Claude Code, Cursor, or CLI.

Copy prompt

Task: Use docs-page in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20docs-page%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/nexu-io-docs-page/install
Install command: npx skills add nexu-io/open-design --skill docs-page
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.

Agent handoff

Give an agent the install path, not another directory page.

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

Open install API

Agent prompt

Use docs-page for this task. Review https://www.openagentskill.com/api/skills/nexu-io-docs-page/install, then install with: npx skills add nexu-io/open-design --skill docs-page

Registry metadata

Agent-readable profile for automatic skill selection.

This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.

Open manifest

Agent fit

100/100

Local desktop

Platforms

Claude Code

Audit report

Needs review · 88/100

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

View audit reportView eval report

Agent decision cockpit

Primary pick for Local desktop

Use this as a leading candidate, then validate the README and install path in your own agent stack.

100
Readiness
Adopt
Stage

Role in stack

Primary pick

Primary fit

Local desktop

Trust label

Production-ready

Install path

Command ready

Use when

  • Local desktop workflows
  • Claude Code teams
  • teams that value GitHub adoption signals

Evidence

  • 90,607 GitHub stars
  • recent repository activity
  • install command or GitHub repo available
  • 96/100 quality profile
  • 1 OpenAgentSkill engagement events

review first

  • No major risk signals from current metadata

Implementation path

  1. 1Install it in a sandbox agent and run one Local desktop task end to end.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

Trust profile

Sandbox only

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

72
OpenAgentSkill Trust Score

GitHub adoption

PASS

91K GitHub stars

Stars/forks activity

PASS

91K stars, 10K forks; issue activity unavailable in current metadata

Recent maintenance

PASS

Pushed today

License clarity

PASS

Apache-2.0

Good signals

  • AI review approved
  • Install path is available
  • Repository evidence is available
  • Recently maintained repository
  • Large GitHub adoption signal
  • Install command has no obvious high-risk pattern
  • Outcome loop is ready but needs first real agent run

Review before install

  • Permission surface needs review: secrets or environment access, shell or command execution
  • Dependency/runtime risk: command execution surface, credential or environment access
  • Permission surface: secrets or environment access, shell or command execution
  • No real agent outcome reports yet
  • Human review required before unattended installation

Recommended action

Run only in a sandbox and compare close alternatives before using it for real work.

Quality profile

Excellent candidate for agent workflows

High-confidence pick with strong adoption and healthy maintenance signals.

96
GitHub stars
91K
Freshness
Today
Install ready
Yes
License
Apache-2.0

Workflow fit

Use this skill in these scenarios

Workflow fit

Add it to a complete workflow

Alternative shortlist

Compare before you install

Similar skills that may fit this task.

Compare all

Overview

--- name: docs-page description: | A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial". triggers: - "docs" - "documentation" - "guide" - "tutorial" - "api reference" - "文档" od: mode: prototype platform: desktop scenario: engineering preview: type: html entry: index.html design_system: requires: true sections: [color, typography, layout, components] craft: requires: [typography, typography-hierarchy, typography-hierarchy-editorial, rtl-and-bidi] ---

# Docs Page Skill

Produce a single, three-column documentation page in one HTML file.

## Workflow

1. **Read the active DESIGN.md** (injected above). Use the body type token for prose; the mono token for code; respect line-height and max-width rules. 2. **Pick a topic** from the brief — the page should look like real docs, not a generic wireframe. Concrete API names, command examples, plausible parameters. 3. **Lay out** three regions, expressed on the inline axis so the layout flips correctly under `dir="rtl"`: - **Inline-start nav** (240–280px, sticky): grouped link list, current page bolded with an `inline-start`-edge accent stripe. 3–5 groups of 4–8 links. - **Article body** (max-width ~720px, centered in the middle column): H1, lede paragraph, H2 sections, code blocks, callout boxes (note / warning), inline links, lists. - **Inline-end TOC** (200–240px, sticky): "On this page" with the H2/H3 anchors, current section highlighted as the user scrolls. 4. **Write** a single HTML document: - `<!doctype html>` through `</html>`, all CSS inline. - CSS Grid for the three columns; sticky positioning for the rails. - Code blocks: monospace token, soft surface fill, copy-button affordance (visual only — no JS needed). - Anchor IDs on every H2/H3 so the TOC links work. - `data-od-id` on the nav, article, and TOC. 5. **Prose**: write at least 350 words of believable docs. Include at least one shell command, one code snippet (5–15 lines), one callout, one table. 6. **Self-check**: - Body text wraps at the DS line-length sweet spot (60–75 chars). - Code uses the DS mono token, not generic `monospace`. - Accent is restrained — used for active nav item, links, one callout border. Not on body text. - Page is readable at 1280w and collapses gracefully below 900w (TOC drops out, nav becomes a top drawer). - Use logical CSS (`margin-inline-start`, `border-inline-start`, `inset-inline-end`, `text-align: start`) on the rails and accent stripe so the layout flips correctly under `dir="rtl"`.

## Output contract

Emit between `<artifact>` tags:

``` <artifact identifier="docs-slug" type="text/html" title="Docs — Page Title"> <!doctype html> <html>...</html> </artifact> ```

One sentence before the artifact, nothing after.

Technical details

Version
1.0.0
License
Apache-2.0
Last updated
Aug 23, 2026
Published
Aug 23, 2026

Decision snapshot

Primary pick

100
Ready
Adopt
Stage

90,607 GitHub stars

Audit

Install review

Install and adoption review

88
Needs review
Security
77/100
Maintenance
100/100
Install
92/100
Open full auditView eval report

Agent-proven evidence

Agent-proven evidence

Outcome reports after resolve, review, install, and one narrow run.

0
Proven
Needs first agent runAuto-install: review firstLast: Unknown
Success rate
Recent failure
Outcomes
0
Output quality
Failed
0
Not relevant
0
Installs
0
Risk blocked
0
Setup needed
0
Production
0

No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.

Install

Add to agent workflow

Free and open source. Review the report before installing into production agents.

Growth loop

Share kit

X

Scenario-led draft for docs-page, ready for a manual X post.

Curator note
A practical pick for design or creative work:

docs-page: A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions...

90.6K stars

https://www.openagentskill.com/skills/nexu-io-docs-page?ref=x
Open X draft
Optional reply with install command
Listing + install path for docs-page:
https://www.openagentskill.com/skills/nexu-io-docs-page?ref=x

Install: npx skills add nexu-io/open-design --skill docs-page

Listing source

Registry indexed

Claimable

This listing was indexed from public sources and is not marked official until a maintainer claim is approved.

Creator
nexu-io
Indexed by
OpenAgentSkill community index

Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.

Claim this skill

Owner claim

Claim this skill listing

This Registry indexed listing is attributed to nexu-io but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.

Creator backlink kit

Add the evidence badges to your README

Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/nexu-io-docs-page?metric=listed&label=Listed)](https://www.openagentskill.com/skills/nexu-io-docs-page)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/nexu-io-docs-page?metric=trust&label=Trust)](https://www.openagentskill.com/skills/nexu-io-docs-page)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/nexu-io-docs-page?metric=audit&label=Audit)](https://www.openagentskill.com/skills/nexu-io-docs-page/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/nexu-io-docs-page?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/nexu-io-docs-page)

Author

N

nexu-io

@nexu-io

Platform fit

Health signals

GitHub stars
90.6K
Quality score
59/100
Last GitHub push
Aug 23, 2026
Framework hints
Unknown
OpenAgentSkill views
1
Install copies
0
Outbound clicks
0

Community signal

Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.

Trust & safety

Sandbox only

72
  • GitHub adoption91K GitHub starsPASS
  • Stars/forks activity91K stars, 10K forks; issue activity unavailable in current metadataPASS
  • Recent maintenancePushed todayPASS
  • License clarityApache-2.0PASS
  • README/SKILL.md completenessMetadata includes enough usage and workflow contextPASS
  • Dependency/runtime riskcommand execution surface, credential or environment accessCHECK