Docs: Quickstart version 2[draft]

[Sushmithamallesh]

Note

Adds a comprehensive Quickstart Preview guide covering SDK setup, auth, tool execution, triggers, MCP server usage, and Tool Router, and links it in the Get Started navigation; bumps Fern config version.

• Docs:
  • New page: fern/pages/src/get-started/quickstart-preview.mdx
    • End-to-end quickstart covering:
      • SDK setup and user auth (OpenAI, Anthropic, LangChain, Vercel AI SDK)
      • Fetching/executing tools and handling tool calls
      • Triggers (create/subscribe/start listening)
      • MCP server setup/usage (Anthropic, OpenAI, Mastra)
      • Experimental Tool Router (session setup and multi-tool workflows)
      • Real-world examples and next steps
  • Navigation: Adds Quickstart Preview to Get Started in fern/docs.yml.
• Config:
  • Bump fern/fern.config.json version to 0.115.2.

^{Written by Cursor Bugbot for commit a5953b5. This will update automatically on new commits. Configure here.}

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review

I've completed a thorough review of the quickstart documentation changes. Here's my comprehensive feedback:

Todo List:

• Read documentation style guide in fern/CLAUDE.md
• Review fern/pages/src/get-started/quickstart-preview.mdx content
• Review fern/docs.yml navigation changes
• Provide comprehensive feedback on grammar, spelling, and clarity
• Check consistency and tone with existing documentation
• Verify adherence to style guide requirements

Review Summary

Overall Assessment: This is a well-structured, comprehensive quickstart guide that effectively covers multiple integration approaches. The content is technically accurate and follows most documentation guidelines. However, there are several areas for improvement regarding style consistency, clarity, and adherence to the documentation style guide.

Navigation Changes (fern/docs.yml)

✅ Proper Integration: The navigation addition is correctly placed and follows the existing structure:

• Added to line 125-127 in the "Get Started" section
• Uses proper slug naming convention (quickstart-preview)
• Points to correct path (pages/dist/get-started/quickstart-preview.mdx)

Content Review (quickstart-preview.mdx)

✅ Strengths

1. Comprehensive Coverage: Excellent coverage of multiple providers and integration methods
2. Progressive Disclosure: Good use of tabs and steps to organize complex information
3. Practical Examples: Code examples are relevant and demonstrate real-world usage
4. Component Usage: Good use of documentation components (Tabs, Steps, CodeGroup, etc.)

⚠️ Issues to Address

1. Title Case Violations (Style Guide Requirement)

The style guide states: "Titles must always start with an uppercase letter, followed by lowercase letters unless it is a name."

Current Issues:

• Line 2: title: Quickstart ✅ (Correct)
• Line 125: page: Quickstart Preview ❌ Should be "Quickstart preview"

2. Grammar and Clarity Issues

Line 41:

**Create an Auth Config for Gmail**

Should be: **Create an auth config for Gmail** (lowercase "auth config" for consistency)

Line 82:

**Connect your users via the auth config**

Should be: **Connect your users through the auth config** (more natural phrasing)

Line 118:

Fetch tools and execute

Should be: Fetch and execute tools (more natural word order)

Line 187:

Create triggers and listen to events

Should be: Create triggers and listen for events (correct preposition)

Line 270:

<Step>

Should be: <Step> (more grammatically correct)

3. Consistency Issues

Mixed Terminology:

• Sometimes uses "Auth Config" (capitalized) and sometimes "auth config" (lowercase)
• Should consistently use lowercase "auth config" except in headings

Code Comment Inconsistencies:

• Line 844: # Router will automatically select tools based on the task
• Line 883: # Router automatically:
• Should consistently use present tense: "Router automatically selects tools..."

4. Technical Content Issues

Line 811:

<Warning>
Tool Router is currently in experimental phase. APIs may change as we continue to improve the feature.
</Warning>

Should be: Tool Router is currently in the experimental phase. (add "the")

Lines 923-924:

</Step>
</Steps>

This appears to be malformed - there's an extra </Step> that doesn't match an opening tag.

5. Link and Reference Issues

Line 262:

See [Triggers documentation](/docs/using-triggers) for more details.

Verify this link is correct based on the navigation structure in docs.yml - it should likely be /docs/triggers/using-triggers

6. Minor Style Issues

Long Paragraphs: Some code blocks could benefit from shorter explanatory text to improve readability.

Line 7: The opening sentence is strong, but could be more concise:
Current: In this quickstart, you'll build an AI agent that can execute real actions across multiple services—from sending emails to creating GitHub issues.
Suggested: Build an AI agent that executes real actions across multiple services—from sending emails to creating GitHub issues.

Recommendations

1. Fix title case: Update "Quickstart Preview" to "Quickstart preview" in docs.yml
2. Standardize terminology: Use consistent capitalization for "auth config" throughout
3. Fix grammar issues: Address the specific grammar and clarity issues noted above
4. Fix structural issues: Correct the malformed Steps/Step tags around lines 923-924
5. Verify links: Ensure all internal documentation links are correct
6. Review experimental warning: Add "the" before "experimental phase"

Style Guide Adherence

✅ Follows Guidelines:

• Uses BLUF approach effectively
• Professional, scientific tone
• Good use of components and structure
• Avoids marketing language

❌ Needs Improvement:

• Title case violations
• Some grammar inconsistencies
• Mixed terminology usage

The content is technically sound and comprehensive. With these style and grammar fixes, it will be an excellent addition to the documentation.

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review Complete

I've thoroughly reviewed the new quickstart preview guide against the documentation style guidelines. Here's my detailed feedback:

Overall Assessment

The quickstart guide is well-structured and comprehensive, following most style guidelines. However, there are several areas for improvement in grammar, consistency, and adherence to the established documentation standards.

Grammar and Spelling Issues

1. Line 7: Missing article - should be "you'll build an AI agent"
2. Line 42: "Auth Configs help you define how users should be authenticated" - should use present tense: "Auth Configs define how users authenticate"
3. Line 118: "Get the tool your agent needs from composio" - capitalization inconsistency, should be "from Composio"
4. Line 187: "Setup triggers" - should be "Set up triggers" (setup is a noun, "set up" is the verb phrase)
5. Line 826: "Initialize with multiple toolkits" - should be "Initialize the session with multiple toolkits"

Style Guide Adherence Issues

1. Title Capitalization:

   • Line 125: "Quickstart Preview" should be "Quickstart preview" (per style guide: uppercase first letter, then lowercase unless it's a name)

2. Marketing Language:

   • Line 3: "Connect AI agents to 500+ tools in under 5 minutes" contains promotional language that should be more factual
   • Line 4: "Build production-ready AI agents" is marketing-focused rather than technical
   • Recommendation: Focus on what users will actually accomplish rather than promotional claims

3. Long Text Blocks:

   • Several paragraphs exceed the recommended length. For example, the Prerequisites section (lines 11-16) should be broken into shorter, more digestible chunks.

Technical Accuracy and Consistency

1. Code Comments: Several code examples include unnecessary comments that don't add value:

   • Line 126: "# Initialize"
   • Line 155: "# Initialize"
   • These should be removed per the style guide's preference for concise, direct content.

2. API Inconsistencies:

   • Line 97: connection_request.wait_for_connection() (Python)
   • Line 112: connectionRequest.waitForConnection() (TypeScript)
   • The method naming is inconsistent - should verify these are the actual API method names.

3. Variable Naming:

   • Mixed use of placeholder values like "your_gmail_client_id" vs actual configuration examples
   • Should be consistent throughout

Structure and Flow Issues

1. Progressive Disclosure: The guide jumps into complex examples without sufficient buildup. Consider:

   • Starting with a single, simple tool execution
   • Then showing authentication
   • Then moving to multi-step workflows

2. Cross-linking: Missing important cross-references:

   • Line 262: References "/docs/using-triggers" but should verify this path exists
   • Need links to authentication setup guides
   • Should link to individual provider documentation

3. Scientific Structure: The document would benefit from clearer logical flow:

   • Current structure: Prerequisites → Execute tools → Examples
   • Recommended: Prerequisites → Basic tool execution → Authentication → Advanced features → Examples

Consistency Issues

1. Terminology:

   • Mixed use of "toolkit" vs "integration" vs "service"
   • "Auth Config" vs "authentication configuration"
   • Should establish consistent terminology

2. Code Style:

   • Inconsistent spacing in code blocks
   • Some examples use print(), others use console.log() - ensure parallel examples are truly parallel

Missing Elements

1. Error Handling: No examples show error handling patterns
2. Rate Limiting: Mentioned in accordion but not demonstrated
3. Testing: No guidance on testing tool integrations

Positive Aspects

✅ Comprehensive Coverage: Covers multiple providers and use cases effectively
✅ Good Use of Components: Excellent use of tabs, accordions, and code groups
✅ Real-world Examples: The examples section provides practical use cases
✅ Progressive Complexity: Generally moves from simple to complex concepts

Recommendations

1. Immediate fixes: Address grammar and spelling issues listed above
2. Tone adjustment: Reduce marketing language, increase technical precision
3. Structure improvement: Add brief introductory paragraphs to each major section
4. Consistency pass: Standardize terminology and code examples
5. Cross-linking: Add links to relevant documentation sections

The navigation change in docs.yml is correctly implemented and follows the existing pattern.

[macroscopeapp]

Add Quickstart Preview docs page to navigation and bump docs config version to 0.115.2

Add a new Quickstart Preview entry in docs navigation and include a new Quickstart MDX page with multi-framework examples; update version to 0.115.2.

📍Where to Start

Start with the new content in fern/pages/src/get-started/quickstart-preview.mdx, then review navigation changes in fern/docs.yml.

---

Macroscope summarized a5953b5.

[claude]

Claude finished @Sushmithamallesh's task —— View job

---

Documentation Review Complete

Todo List:

• Read documentation style guide in fern/CLAUDE.md
• Review fern/pages/src/get-started/quickstart-preview.mdx content
• Review fern/docs.yml navigation changes
• Review fern/fern.config.json version bump
• Provide comprehensive feedback on grammar and spelling
• Check clarity and readability
• Verify consistency and tone
• Ensure proper adherence to style guide requirements
• Provide constructive recommendations

---

Review Summary

I've thoroughly reviewed the quickstart preview documentation against the style guide requirements. Here's my comprehensive feedback:

✅ Positive Aspects

• Comprehensive Coverage: Excellent coverage of multiple integration approaches (Tools, MCP Server, Tool Router)
• Good Structure: Effective use of tabs, steps, and accordions for organization
• Practical Examples: Relevant code examples across multiple providers
• Technical Accuracy: Code examples appear correct and demonstrate real usage patterns

❌ Issues Requiring Attention

1. Style Guide Violations

Title Case Issues (Line 125 in docs.yml):

• Current: page: Quickstart Preview
• Should be: page: Quickstart preview
• Style guide states: "Titles must always start with an uppercase letter, followed by lowercase letters unless it is a name"

2. Grammar and Language Issues

Line 3: subtitle: Connect AI agents to 500+ tools in under 5 minutes

• Contains promotional/marketing language which violates the "no marketing language or fluff" guideline
• Suggested: subtitle: Connect AI agents to external tools and services

Line 4: description: "Build production-ready AI agents with real-world tool access"

• Marketing-focused language ("production-ready")
• Suggested: description: "Learn to integrate AI agents with external tools using Composio"

Line 41: **Create an Auth Config for Gmail**

• Inconsistent capitalization
• Should be: **Create an auth config for Gmail**

Line 82: **Connect your users via the auth config**

• Awkward phrasing
• Suggested: **Connect your users through the auth config**

Line 118: Fetch tools and execute

• Incomplete/awkward phrasing
• Suggested: Fetch and execute tools

Line 187: Setup triggers

• Incorrect verb form (setup is a noun)
• Should be: Set up triggers

Line 811: Tool Router is currently in experimental phase

• Missing article
• Should be: Tool Router is currently in the experimental phase

3. Technical and Structural Issues

Lines 923-924: Malformed markup

</Step>
</Steps>

• Extra closing </Step> tag without matching opening tag
• Fix: Remove the extra </Step>

Line 262: Link verification needed

See [Triggers documentation](/docs/using-triggers) for more details.

• Verify this path exists in the navigation structure

4. Consistency Issues

Mixed Terminology:

• Sometimes "Auth Config" (capitalized)
• Sometimes "auth config" (lowercase)
• Recommendation: Use lowercase "auth config" consistently except in headings

Code Comments:

• Line 844: # Router will automatically select tools based on the task
• Line 883: # Router automatically:
• Should be consistent: Use present tense throughout

5. Style Guide Adherence

BLUF Principle:

• Line 7 could be more concise
• Current: In this quickstart, you'll build an AI agent that can execute real actions across multiple services—from sending emails to creating GitHub issues.
• Suggested: Build an AI agent that executes actions across multiple services—from sending emails to creating GitHub issues.

Long Text Blocks:

• Several paragraphs could be broken into shorter, more digestible chunks
• Prerequisites section (lines 11-16) is dense

📋 Navigation and Config Changes

✅ docs.yml: Navigation addition is correctly structured and placed
✅ fern.config.json: Version bump to 0.115.2 is appropriate

📝 Recommendations

1. Immediate fixes needed:

   • Fix title case in docs.yml (line 125)
   • Remove marketing language from subtitle/description
   • Fix malformed HTML tags (lines 923-924)
   • Standardize "auth config" terminology

2. Style improvements:

   • Make opening sentence more direct and concise
   • Break up long paragraphs for better readability
   • Verify all internal documentation links

3. Consistency pass:

   • Use consistent capitalization for technical terms
   • Ensure parallel structure in code comments
   • Standardize variable naming patterns in examples

The content is technically sound and comprehensive. With these fixes, it will fully align with the documentation style guide and provide an excellent user experience.

---

[claude]

Claude Code is working…

I'll analyze this and get back to you.

View job run

[cursor]

Bug: Tool Router: Incomplete Session Configuration

The Tool Router example attempts to use GITHUB_SEARCH_ISSUES in a workflow, but the session was created with only gmail, calendar, slack, and notion toolkits. The github toolkit is missing from the session configuration, so the router won't have access to GitHub tools and this example will fail when executed.

 

[github-actions]

Preview your docs: https://composio-preview-afdc24c1-cbe9-4231-9323-5265caa10e5d.docs.buildwithfern.com