Skip to content

docs: recommend Notte skill workflow#814

Closed
leo-notte wants to merge 1 commit into
mainfrom
docs/notte-skill-workflow
Closed

docs: recommend Notte skill workflow#814
leo-notte wants to merge 1 commit into
mainfrom
docs/notte-skill-workflow

Conversation

@leo-notte
Copy link
Copy Markdown
Contributor

@leo-notte leo-notte commented May 11, 2026

Summary

  • update the site-wide docs banner to recommend starting with the Notte skill before SDK automation
  • link directly to the notte-skills repository
  • revise index and quickstart human-facing copy to explain when to use the skill versus SDK

Checks

  • pre-commit hooks via git commit
  • jq empty docs/src/docs.json

Summary by CodeRabbit

  • Documentation
    • Updated setup guidance to recommend a two-phase workflow: start with Notte skill exploration to validate browser flows, then transition to SDK development for repeatable actions.
    • Enhanced quickstart instructions with clearer recommendations for when to use Notte skill vs SDK, including guidance for AI-assisted workflows.

Note

Updates docs banner, index, and quickstart copy to recommend starting with the Notte skill for exploration before moving to the SDK for repeatable automation. Removes the inline bash install snippet from two pages and replaces it with prose linking to the notte-skills GitHub repo.

Written by Mendral for commit 56f67e5.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 11, 2026

Walkthrough

This PR updates the onboarding documentation across three files to revise the recommended setup workflow. The changes promote a two-phase approach: first using the Notte skill for browser flow discovery and validation on live pages, then transitioning to the SDK once the workflow is known and repeatable. The banner in docs.json, intro guidance in index.mdx, and quickstart instructions in quickstart.mdx all receive updated messaging aligned with this workflow recommendation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • nottelabs/notte#771: Updates docs.json content that is consumed by generate\_llms.py to produce the docs/src/llms.txt file
  • nottelabs/notte#773: Both PRs modify the same set of onboarding documentation files (docs/src/index.mdx, docs/src/quickstart.mdx, and docs/src/docs.json) to align the getting-started and quickstart messaging
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: recommend Notte skill workflow' clearly and concisely summarizes the main change: updating documentation to recommend the Notte skill workflow as a starting point before SDK automation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/notte-skill-workflow

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
docs/src/docs.json (1)

16-16: ⚡ Quick win

Consider reordering the banner for clearer user flow.

The current banner mentions "start with the [Notte skill]... then automate with the SDK; install it with..." This presents the steps out of logical order (skill → SDK → install skill). Users would naturally expect: install → use → then automate.

Additionally, "install it" is ambiguous—readers may wonder whether "it" refers to the skill or SDK.

✍️ Proposed rewording for clearer flow
-    "content": "Recommended workflow: start with the [Notte skill](https://github.com/nottelabs/notte-skills/), then automate with the SDK; install it with `npx skills add nottelabs/notte-skills` | [Setup guide](/integrations/claude-code-ai-agents)",
+    "content": "Recommended workflow: install the [Notte skill](https://github.com/nottelabs/notte-skills/) with `npx skills add nottelabs/notte-skills` to explore browser flows, then automate with the SDK | [Setup guide](/integrations/claude-code-ai-agents)",
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/src/docs.json` at line 16, Reorder and reword the "content" string in
docs.json so the user flow is install → try → automate: first tell users to
install the Notte skill (explicitly name the skill, e.g., "install the Notte
skill with `npx skills add nottelabs/notte-skills`"), then say "start with the
Notte skill" (or "try the Notte skill") and finally mention automating with the
SDK ("then automate with the SDK"). Update the sentence assigned to the
"content" key to remove the ambiguous "install it" pronoun and make each step
explicit and sequential.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/src/docs.json`:
- Line 16: Reorder and reword the "content" string in docs.json so the user flow
is install → try → automate: first tell users to install the Notte skill
(explicitly name the skill, e.g., "install the Notte skill with `npx skills add
nottelabs/notte-skills`"), then say "start with the Notte skill" (or "try the
Notte skill") and finally mention automating with the SDK ("then automate with
the SDK"). Update the sentence assigned to the "content" key to remove the
ambiguous "install it" pronoun and make each step explicit and sequential.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0e4e6e71-f0f9-4e6e-b0e2-acf3b894fd17

📥 Commits

Reviewing files that changed from the base of the PR and between 767ce11 and 56f67e5.

📒 Files selected for processing (3)
  • docs/src/docs.json
  • docs/src/index.mdx
  • docs/src/quickstart.mdx

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 11, 2026

Greptile Summary

This PR updates the site-wide docs banner and the human-facing copy on the index and quickstart pages to recommend a two-phase workflow: use the Notte skill to explore and validate a browser flow first, then move to the SDK for repeatable automation.

  • docs/src/docs.json: Banner rewritten to surface the skill → SDK workflow recommendation alongside the npx skills add install command.
  • docs/src/index.mdx: Human Tip block and "Getting Started" intro updated to explain when to use the Notte skill vs. the SDK; agent-facing block unchanged.
  • docs/src/quickstart.mdx: Human Tip block replaced with conceptual guidance; prose before the SDK examples updated to reference the Notte skill for initial flow validation.

Confidence Score: 4/5

Documentation-only change with no logic or configuration modified; safe to merge with the two minor copy clarifications addressed.

All three files are docs-only edits. The only issues found are a dangling "the CLI" reference in quickstart.mdx and an ambiguous pronoun in the banner — both easily resolved with the inline suggestions provided.

docs/src/quickstart.mdx (dangling CLI reference on line 66) and docs/src/docs.json (banner pronoun ambiguity).

Important Files Changed

Filename Overview
docs/src/docs.json Banner text updated to recommend the two-phase skill → SDK workflow; new text contains a slightly ambiguous "it" pronoun but no functional issues.
docs/src/index.mdx Human-facing Tip block and "Getting Started" intro revised to recommend the Notte skill for exploration before using the SDK; agent-facing block left unchanged.
docs/src/quickstart.mdx Human Tip block updated; line 66 now references "the CLI" without any prior mention of a CLI tool in the human-visible section, creating a dangling reference.

Fix All in Claude Code

Prompt To Fix All With AI
Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
docs/src/quickstart.mdx:66
After this PR's edits, the human-visible `<Visibility for="humans">` Tip block no longer mentions any CLI tool — it only links to the Notte skill GitHub repo. The sentence below therefore leaves "the CLI" undefined for human readers. Replacing it with "the Notte skill" keeps the reference consistent with what was introduced above.

```suggestion
Both Python and JavaScript quickstarts below use the official Notte SDK. Start with Browser Session if you already know the flow you want to automate, or after you have validated it with the [Notte skill](https://github.com/nottelabs/notte-skills/).
```

### Issue 2 of 2
docs/src/docs.json:16
The pronoun "it" in "install it with `npx skills add nottelabs/notte-skills`" has two possible referents in the sentence — the Notte skill and the SDK. Replacing "it" with "the skill" removes the ambiguity.

```suggestion
    "content": "Recommended workflow: start with the [Notte skill](https://github.com/nottelabs/notte-skills/), then automate with the SDK; install the skill with `npx skills add nottelabs/notte-skills` | [Setup guide](/integrations/claude-code-ai-agents)",
```

Reviews (1): Last reviewed commit: "docs: recommend Notte skill workflow" | Re-trigger Greptile

@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 11, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Nottelabs 🟢 Ready View Preview May 11, 2026, 11:18 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@2027-evals
Copy link
Copy Markdown

2027-evals Bot commented May 11, 2026

✅ Eval complete for commit 56f67e5

URL Mapping
docs.notte.cc notte-docs-notte-skill-workflow.mintlify.app

Ran evals with prompts:

📈 +0.9 pts · Getting Started — B (78.6/100) from B (77.7) · View metrics

Prompt text:

Use Notte to run a headless browser session. Follow the quickstart at https://notte.cc/ to set up a project that:

  1. Creates a cloud browser session
  2. Connects to it using Playwright, Puppeteer, or the Notte SDK
  3. Navigates to https://news.ycombinator.com
  4. Extracts the titles of the top 5 stories
  5. Prints them to stdout

Verdict:

Notte delivers one of the better AI-agent onboarding experiences — a dedicated SKILL.md, Context7 indexing, an MCP server, a published OpenAPI spec, and a typed SDK — but the incomplete TypeScript declarations for the .use() pattern are a notable gap at the SDK layer.

Friction points:

  • 🔴 The Session — .use() context-manager method exists at runtime in index.mjs but is absent from the TypeScript declaration file (index.d.ts), requiring the agent to inspect the raw .mjs source to confirm it was safe to use.
  • 🟡 The TypeScript declaration file is 67 000+ tokens — larger than most LLM context windows — making it impractical for an AI agent to read in one pass; splitting it or adding a concise summary type file would help.
  • 🟡 The session — .status() response shape (including cdp_url) is not prominently documented in the quickstart; agents must infer it from TypeScript types or runtime experimentation.

Result: B (78.6/100)

delta vs baseline: +0.9 pts

Dimension Baseline This PR
Setup Friction 86 100
Speed 85 85
Efficiency 41 39
Error Recovery 100 100
Doc Quality 80 70

Stats: 1m 58s · 25 tool calls · 0 errors · $1.36

View report → · View trace →


Evaluating agent experience using 2027.dev · View dashboard

Copy link
Copy Markdown

@mendral-app mendral-app Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Pure documentation copy changes with no security, correctness, or data-loss concerns. The messaging is clear and consistent across all three files.

Tag @mendral-app with feedback or questions. View session

@leo-notte
Copy link
Copy Markdown
Contributor Author

Superseded by #815, which includes this commit plus the follow-up quickstart and snippet updates in one PR.

@leo-notte leo-notte closed this May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant