Exa connector and tools by Pranesh-Raghu · Pull Request #498 · scalekit-inc/developer-docs

Pranesh-Raghu · 2026-03-15T14:02:58Z

Summary by CodeRabbit

Documentation
- Added comprehensive Exa agent connector docs: step-by-step setup for registering and storing Exa API keys, instructions to add connected accounts (dashboard & API), Python proxy usage examples, and tips on API-key auth, credits, and rate limits.
- New reference guide detailing seven capabilities: exa_search, exa_find_similar, exa_crawl, exa_get_contents, exa_answer, exa_research, exa_websets.

- Rewrote _setup-exa.mdx with 3-step guide: generate API key, create Scalekit connection, add connected account (dashboard + programmatic via upsert_connected_account) - Rewrote _usage-exa.mdx with direct actions.request() pattern (API Key auth, no OAuth flow) - Added UsageExaSection export to index.ts - Added Usage section to exa.mdx referencing UsageExaSection - Added clean dashboard mockup screenshots: create-api-key.png, add-credentials.png, add-connected-account.png

coderabbitai · 2026-03-15T14:03:25Z

Walkthrough

Adds Exa connector documentation: two template MDX sections (setup and usage), exports them from the agent-connectors template index, and a new reference page detailing Exa capabilities, auth, examples, and parameter tables.

Changes

Cohort / File(s)	Summary
Exa Setup & Usage templates `src/components/templates/agent-connectors/_setup-exa.mdx`, `src/components/templates/agent-connectors/_usage-exa.mdx`	New MDX docs: guided setup (API key creation, connection, upserting connected accounts) and usage examples (Python proxy requests, client setup, tips).
Template exports `src/components/templates/agent-connectors/index.ts`	Added exports for `SetupExaSection` and `UsageExaSection` to surface the new templates.
Exa reference page `src/content/docs/reference/agent-connectors/exa.mdx`	New reference page with front matter, hero, imported setup/usage sections, auth badge, and detailed capability descriptions and parameter tables for Exa agent functions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Apollo connectors and tools #475: Adds agent-connector MDX templates and updates the same agent-connectors/index.ts exports—same pattern as this change.
feat: extract agent connector usage sections into templates #489: Introduced extracted usage templates and index exports for connectors; closely related templating/export changes.
Upgrades the agent connectors docs #455: Similar additions of connector setup/usage MDX templates and corresponding index export updates.

Suggested reviewers

saif-at-scalekit
ravibits
amitash1912
Avinash-Kamath

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Exa connector and tools' accurately describes the main changes, which add new Exa agent connector documentation and setup/usage files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📝 Coding Plan

Generate coding plan for human review comments

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

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/components/templates/agent-connectors/_setup-exa.mdx`:
- Around line 45-49: Replace the hard-coded API key literal in the call to
scalekit_client.actions.upsert_connected_account (the credentials={"api_key":
"your-exa-api-key"} argument) with a value read from a secure source at runtime
(e.g., an environment variable or a secrets manager) before passing into
connection_name="exa" and identifier="user_123"; ensure the example demonstrates
retrieving the API key (e.g., from os.environ or a runtime input) and then calls
upsert_connected_account with credentials={"api_key": api_key_variable} so no
secret is embedded in the example.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 04ab0d3e-dd85-4577-be7b-2b4e9a968515

📥 Commits

Reviewing files that changed from the base of the PR and between 0649378 and baa86b9.

⛔ Files ignored due to path filters (3)

src/assets/docs/agent-connectors/exa/add-connected-account.png is excluded by !**/*.png
src/assets/docs/agent-connectors/exa/add-credentials.png is excluded by !**/*.png
src/assets/docs/agent-connectors/exa/create-api-key.png is excluded by !**/*.png

📒 Files selected for processing (4)

src/components/templates/agent-connectors/_setup-exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts
src/content/docs/reference/agent-connectors/exa.mdx

📜 Review details

🧰 Additional context used

📓 Path-based instructions (11)

**/*.mdx

📄 CodeRabbit inference engine (.cursorrules)

**/*.mdx: Use clear, descriptive titles that explain the purpose of the document
Include comprehensive descriptions in frontmatter metadata
Organize content with logical heading hierarchy (H2, H3, H4)
Use tableOfContents property in frontmatter when content has multiple sections
Set appropriate sidebar labels for navigation in frontmatter
Use direct instruction writing style with phrases like 'This guide shows you how to...' and 'Create an authorization URL to...'
Use second person perspective ('your application', 'you receive', 'you must') in documentation
Keep sentences concise, aiming for under 25 words per sentence
Explain the 'why' in documentation with phrases like 'This prevents CSRF attacks by...' or 'Use this to validate that...'
Use action verbs in section headings: 'Store session tokens securely', 'Validate the state parameter', 'Exchange authorization code for tokens'
Use present tense for descriptions: 'Scalekit handles the complex authentication flow', 'The SDK provides methods to refresh tokens'
Use future tense for results: 'This will redirect users to...', 'You'll receive a JWT containing...', 'Scalekit returns an authorization code'
Use transition phrases between sections: 'After the user authenticates...', 'Once the state is validated...', 'Let's take a look at how to...'
Write 1-3 opening paragraphs that explain what users will accomplish, provide context about when/why, preview key concepts, and use direct instructional language
Begin introduction sections with a clear statement of what the guide covers and explain the problem being solved
Use collapsible sections in introduction for sequence diagrams, video demonstrations, data models, and JSON examples with appropriate icons
Use numbered format within Steps component: 1. ## Title with all step content indented with exactly 3 spaces
Use action-oriented headings in step-by-step guides within Steps components
Include code examples in all 4 languages (Node.js, Python, Go, Java) within Steps co...

Files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

⚙️ CodeRabbit configuration file

**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:

Frontmatter

title MUST be ≤ 60 characters and clearly state what the page does.

description MUST be ≤ 160 characters, action-oriented, unique per page.

sidebar.label MUST be present and ≤ 30 characters.

sidebar.order MUST be set on every page that lives inside a section
with siblings, to enforce the journey order in sidebar.config.ts.

Flag any missing prev / next links on pages that are clearly
part of a sequential flow (e.g., quickstart → implement-login →
complete-login → manage-session → logout).

Voice & Style (CLAUDE.md standards)

Voice: confident, direct, collaborative, instructional.

Person: second person only ("you", "your application"). Reject "we",
"our", "the developer", "the user".

Tense: present tense for descriptions; imperative mood for instructions.

Flag weasel words: "simply", "just", "easy", "straightforward",
"obviously", "of course", "note that".

Flag passive voice constructions where active voice is clearer.

Headings must be sentence case, not Title Case (except proper nouns).

No heading should end with a colon or period.

Content structure

How-to guides MUST contain numbered <Steps> (Starlight component).

Concept pages MUST NOT contain numbered steps — concepts explain, not instruct.

API reference pages MUST list parameters in a table with Name / Type /
Required / Description columns.

Every page MUST end with a clear "what's next" signal — either a
next: frontmatter link, a <LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.

Code examples

ALL code examples that show SDK usage MUST include all four language
tabs: Node.js, Python, Go, Java — using <Tabs syncKey="tech-stack">.

SDK variable names are STRICTLY: scalekit (Node.js),
scalekit_client (Python), scalekitClient (Go), ...

Files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

**/*.{yml,yaml,md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/browsecentral-labels.mdc)

**/*.{yml,yaml,md,mdx}: BrowseCentral labels should be maximum 3-5 words - keep concise but add context when needed
BrowseCentral labels should be action-oriented - start with verbs when possible
BrowseCentral labels should be specific and clear - add context when simple labels are ambiguous
BrowseCentral labels should be outcome-focused - describe what users accomplish and the context
BrowseCentral labels should use 'Action + Object' pattern (e.g., 'Invite users', 'Restrict sign-up', 'Set up SCIM')
BrowseCentral labels should use feature names (e.g., 'Enterprise SSO', 'Passwordless quickstart')
BrowseCentral labels should describe task completion (e.g., 'Run migrations', 'Migrate auth', 'Merge identities')
BrowseCentral labels should include specific context when needed (e.g., 'Configure Scalekit MCP server', 'Validate incoming API requests')
BrowseCentral labels should use integration context when applicable (e.g., 'Build MCP auth with your existing auth system')
BrowseCentral labels should avoid instructional prefixes: 'How to', 'Guide to', 'Implement', 'Configure', 'Learn', 'Understand'
BrowseCentral labels should avoid verbose phrases: 'Step-by-step guide', 'Complete tutorial', 'Detailed documentation'
BrowseCentral labels should avoid weak verbs: 'Enable', 'Allow', 'Provide', 'Support'

Files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/deno-docs-style.mdc)

**/*.{md,mdx}: Use sentence case for all titles and headings in MD/MDX documentation
Keep page titles short and descriptive (3–7 words when possible) in MD/MDX documentation
Use outcome-focused headings that describe results, not categories (e.g., 'Run a script' not 'Scripts')
Avoid gerunds in headings when an imperative works - prefer 'Configure proxies' over 'Configuring proxies'
Keep sidebar labels concise (1–3 words), use sentence case, and focus on outcomes or objects
Use sentence case in sidebar labels without punctuation
Set frontmatter title in sentence case with a clear outcome; description in one sentence (≤160 chars); sidebar.label as shorter form of title; enable tableOfContents on longer pages
Start documentation pages with a one-paragraph overview explaining what the page covers and when to use it
Present the primary use case (80% path) first in documentation, with edge cases later
Use numbered steps for task-focused sections in documentation, with each step beginning with a verb
Break up long documentation sections with subheadings every 3–6 paragraphs
Use asides for important notes, tips, cautions, and references in documentation
Provide runnable, minimal code examples that work as-is in documentation
Prefer CLI-first examples and show file layout when helpful in documentation
Label code blocks with titles for context (e.g., 'Terminal', 'main.ts') in documentation
Keep code block annotations brief and purposeful - annotate only what matters
Use consistent variable and file names across a documentation page
Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')
Prefer relative links for internal documentation pages and include anchors for section references
Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints
Use backticks for code, file names, CLI flags, and endpoints in documentation
Use lists for options and features in documentation; tables only when comparisons are cleare...

Files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

src/content/docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (CLAUDE.md)

src/content/docs/**/*.{md,mdx}: Product-based documentation (MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, Modular SSO) MUST follow a journey-focused approach. Each product represents a developer's journey toward implementing authentication in their projects.
Proactively address common setup and configuration problems. Keep code examples simple, self-contained, and exportable.
Use imperative for procedures: 'Install', 'Create', 'Run', 'Configure', 'Test'. Front-load the action and start sentences with the verb or key concept.
Explain why when useful. Briefly justify non-obvious steps. Prefer examples over theory; show the common path first and link to details.
Every page MUST include frontmatter with at least: title (≤60 characters), description (≤160 characters), and sidebar.label (1-3 words). Use sidebar.order only when navigation ordering matters. Use prev/next for sequential guides; use seeAlso for related guides. Enable tableOfContents for longer pages with multiple major sections.
Opening paragraphs (1-3) MUST state what users will accomplish, when/why they need it, and preview the workflow using direct instructional language
The Steps component requires a single continuous ordered list. Steps must start at column 0 with no leading spaces. Continuation content (images, text) must be indented with exactly 3 spaces. Sub-bullet lists use 3 spaces with no blank line before bullets. No blank line immediately after Steps opening tag.
Documentation must be organized into logical sections (FSA, SSO, Directory/SCIM, Connect, M2M, Guides, Reference) with proper sidebar configuration and navigation structure

Files:

src/content/docs/reference/agent-connectors/exa.mdx

**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy,gradle,xml,json}

📄 CodeRabbit inference engine (.cursor/rules/comment-standards.mdc)

Comments should not duplicate the code - avoid comments that simply restate what the code does; comments should add value beyond what's obvious from reading the code

Files:

src/components/templates/agent-connectors/index.ts

**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy}

📄 CodeRabbit inference engine (.cursor/rules/comment-standards.mdc)

**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy}: Good comments do not excuse unclear code - refactor the code to be self-explanatory instead of using comments to explain poorly written code; use better variable names, function names, and code structure
Comments should dispel confusion, not cause it - ensure comments clarify rather than obscure the code's purpose; avoid cryptic or joke comments
Explain unidiomatic code in comments - comment on code that might seem unnecessary or redundant and document why you chose a specific pattern over more common alternatives, especially when it deviates from team conventions
Provide links to the original source of copied code - always attribute code copied from external sources with URLs to Stack Overflow answers, GitHub repositories, or documentation
Include links to external references where helpful - reference standards, RFCs, and official documentation; link to relevant specifications when implementing protocols
Add comments when fixing bugs - document bug fixes with context about the issue, reference issue trackers and bug reports, and explain workarounds and their limitations
Use comments to mark incomplete implementations - use standard formats for TODO, FIXME, and NOTE comments with context about what needs to be done and reference issue trackers when possible
Always document public APIs with function/class comments - explain the purpose, parameters, return values, and exceptions; include usage examples for complex functions
Include file headers with copyright information, license, and authorship - provide a brief description of the file's purpose and document dependencies and requirements

Files:

src/components/templates/agent-connectors/index.ts

**/*.{js,ts,tsx,jsx}

📄 CodeRabbit inference engine (.cursor/rules/comment-standards.mdc)

Use JSDoc standards for all function, class, and complex logic comments in JavaScript/TypeScript - include parameter descriptions (@param), return values (@returns), types (@type), and descriptions; document exceptions and edge cases

Files:

src/components/templates/agent-connectors/index.ts

**/*.{ts,tsx,js,jsx,py,go,java}

📄 CodeRabbit inference engine (CLAUDE.md)

Comments should not duplicate the code. Do not use comments to explain poorly written code; instead, use better variable names and structure. Comments should dispel confusion, not cause it.

Files:

src/components/templates/agent-connectors/index.ts

**/*.{ts,tsx,js,jsx,java,py}

📄 CodeRabbit inference engine (CLAUDE.md)

Use JSDoc/JavaDoc/docstring standards for function, class, and complex logic comments. Include parameter descriptions, return values, types, and descriptions. Document exceptions and edge cases.

Files:

src/components/templates/agent-connectors/index.ts

**/*.{ts,tsx,js,jsx,java,py,go}

📄 CodeRabbit inference engine (CLAUDE.md)

**/*.{ts,tsx,js,jsx,java,py,go}: Add comments when fixing bugs; reference issue trackers. Use standard formats for TODO, FIXME, and NOTE comments.
Include links to external references in comments where helpful (standards, RFCs, official documentation)

Files:

src/components/templates/agent-connectors/index.ts

**/*.{ts,js,mjs}

⚙️ CodeRabbit configuration file

**/*.{ts,js,mjs}: Do NOT enforce code-commenting style rules on these files.
Specifically, do not flag:

Comments that "duplicate" or restate what the code does.

Missing comments on bug fixes, workarounds, or issue references.

Missing inline documentation or explanatory comments.
Code comments are at the author's discretion.

Files:

src/components/templates/agent-connectors/index.ts

🧠 Learnings (48)

📓 Common learnings

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 0
File: :0-0
Timestamp: 2026-03-13T04:24:59.653Z
Learning: In scalekit-inc/developer-docs, for PRs focused on tooling and templatizing (e.g., extracting usage sections into reusable MDX templates and updating sync scripts), review comments about .mdx file content quality (casing, unused imports, import consolidation, endpoint descriptions, etc.) are considered out of scope and should be resolved without blocking the PR.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:44.897Z
Learning: For any agent connector documentation files located in src/content/docs/reference/agent-connectors/, use CDN URLs for connector logos with the host `https://cdn.scalekit.com/sk-connect/assets/provider-icons/` (e.g., `https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg`). The correct host is `cdn.scalekit.com`, NOT `cdn.scalekit.cloud`. Do not flag or change image src attributes that use `cdn.scalekit.com` for provider icons in this directory.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:27.672Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, do not enforce the 160-character description limit. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may have longer descriptions from the source data.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:56.400Z
Learning: For Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), currently only Python SDK support is available for Agent Actions/Agent Connectors. Do not require or enforce the multi-language SDK code examples (Node.js, Python, Go, Java) guideline for these connector docs until SDK support is ready in other languages. The Node.js, Go, and Java examples can be added once the respective SDKs support Agent Actions features.

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

📚 Learning: 2026-02-26T07:22:49.128Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:23:24.179Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-13T03:44:16.883Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:16.883Z
Learning: In MDX files under src/content/docs/reference/agent-connectors, specifically simple connector-header div blocks used for the header grid layout (e.g., a 5-column grid with description and logo), treat the absence of a justification comment as acceptable/readable. Do not flag or require a justification comment for these simple header div blocks in agent-connector reference pages.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:21:32.951Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:18:41.518Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:20:42.107Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-12T16:28:42.817Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include comprehensive descriptions in frontmatter metadata

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Test MDX documentation locally before committing to catch parsing and Steps component indentation errors

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-03T13:35:47.638Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:47.638Z
Learning: In Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), only Python SDK examples for Agent Actions/Agent Connectors should be required for now. Do not enforce or require multi-language SDK code examples (Node.js, Python, Go, Java) until the respective SDKs support Agent Actions. Once supported, you can add and require other languages in those docs. This guideline applies to all files under the agent-connectors documentation path.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-01-30T18:18:50.883Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-04T12:47:16.544Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T08:57:12.201Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T13:04:27.491Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-05T11:29:08.125Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 463
File: src/content/docs/agent-auth/providers.mdx:35-73
Timestamp: 2026-03-05T11:29:08.125Z
Learning: In src/content/docs/agent-auth/providers.mdx, the Card components intentionally use icon=" " (a space) to render consistent colored boxes since some Starlight icon names resolve to icons and others do not. Do not flag icon=" " as a placeholder issue for this file; treat this as a deliberate UX choice specific to this MDX page and avoid raising a placeholder-icon warning here.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-09T07:27:56.794Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 469
File: src/content/docs/guides/integrations/scim-integrations/azure-scim.mdx:95-107
Timestamp: 2026-03-09T07:27:56.794Z
Learning: Do not enforce the 3-space indentation rule for Steps component content as a hard style rule in MDX files under src/content/docs/**/*.mdx. Only flag/rectify it if it causes visible rendering problems in the UI. Otherwise, allow current formatting; apply this rule only when rendering issues are observed and document any fixes.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-09T07:32:38.426Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 467
File: src/content/docs/sso/guides/sso-user-attributes.mdx:108-148
Timestamp: 2026-03-09T07:32:38.426Z
Learning: In MDX code samples under src/content/docs (and similar conceptual snippets in scalekit-inc/developer-docs), when an example's sole purpose is to show how to access a specific value (e.g., reading JWT claims after token validation), omit error/non-happy-path handling to keep the snippet focused. Do not flag the absence of error paths in narrowly scoped conceptual snippets.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T03:34:41.147Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:31-31
Timestamp: 2026-02-25T03:34:41.147Z
Learning: In MDX files, import { Code } from 'astrojs/starlight/components' only if the MDX content actually uses the <Code> component. If the file uses only fenced code blocks (```), the import is not required. Apply this guideline to all MDX files (e.g., src/content/docs/**/*.mdx) to avoid unnecessary imports and reduce bundle size.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-25T18:41:00.639Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 446
File: src/content/docs/authenticate/m2m/api-auth-quickstart.mdx:78-78
Timestamp: 2026-02-25T18:41:00.639Z
Learning: Preserve full URLs inside code comments in MDX code blocks (bash/python/js) when the URLs are part of copyable examples. Do not flag these in code examples. Use relative paths in prose and hyperlinks within MDX; only enforce relative paths for markdown prose links, not for URLs inside code comments.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx
src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-13T03:51:40.660Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:40.660Z
Learning: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/ (e.g., https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg). The host should be cdn.scalekit.com (not cdn.scalekit.cloud). Do not flag or modify image src attributes that already use cdn.scalekit.com for provider icons within this directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:22:55.583Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:55.583Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, the parameter tables (showing tool properties) are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Any table format corrections must be made in the generation script, not by manually editing the generated MDX files. The script should be updated to output the required "Name | Type | Required | Description" four-column table format per coding guidelines.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include configuration comments in code examples: '// Get the signing secret from Scalekit dashboard > Interceptors tab'

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:23:27.672Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:27.672Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, do not enforce the 160-character description limit. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may have longer descriptions from the source data.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:21:37.207Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:37.207Z
Learning: In src/content/docs/reference/agent-connectors/** MDX files, tool headings (e.g., `googlesheets_create_spreadsheet`, `googlesheets_get_values`) intentionally use H2 (##) instead of H3 to ensure they appear in the table of contents for easier navigation. This is a deliberate UX choice for agent connector reference pages and should not be flagged as a hierarchy issue.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include use case comments explaining scenarios in code examples: '// Use case: Provision a workspace after a sales-assisted onboarding'

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Use Tabs/TabItem components for multi-language or multi-framework examples in MDX documentation

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-03-13T04:24:59.653Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 0
File: :0-0
Timestamp: 2026-03-13T04:24:59.653Z
Learning: In scalekit-inc/developer-docs, for PRs focused on tooling and templatizing (e.g., extracting usage sections into reusable MDX templates and updating sync scripts), review comments about .mdx file content quality (casing, unused imports, import consolidation, endpoint descriptions, etc.) are considered out of scope and should be resolved without blocking the PR.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx

📚 Learning: 2026-03-09T15:06:49.617Z

Learnt from: hrishikesh-p
Repo: scalekit-inc/developer-docs PR: 473
File: src/content/docs/agent-auth/tools/execute.mdx:34-76
Timestamp: 2026-03-09T15:06:49.617Z
Learning: In src/content/docs/agent-auth/tools/**/*.mdx (Agent Auth tool execution docs, e.g., execute.mdx, authorize.mdx), only Python and Node.js SDK support is currently available for Agent Auth tool execution. Do not require or enforce Go and Java tabs in Tabs syncKey="tech-stack" blocks for these files until the Go and Java SDKs support Agent Auth features. Add Go and Java TabItems once those SDKs are ready.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx

📚 Learning: 2026-02-26T07:18:51.377Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:51.377Z
Learning: In src/content/docs/reference/agent-connectors/**/*.mdx files, sidebar.label frontmatter is not required because the sidebar configuration references the agent-connectors directory for auto-generation. Navigation ordering and grouping are managed centrally in the sidebar configuration file.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-02T05:55:51.251Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/native-app.mdx:72-179
Timestamp: 2026-02-02T05:55:51.251Z
Learning: In the `src/content/docs/authenticate/fsa/multiapp/` directory, the multi-app authentication documentation (native-app.mdx, single-page-app.mdx, web-app.mdx, overview.mdx) currently uses conceptual shell/curl examples instead of multi-language SDK code examples because the Scalekit SDKs have not yet been built/updated for multi-app functionality. Once the SDKs are ready, these files should be updated to include all 4 languages (Node.js, Python, Go, Java) using `<Tabs syncKey="tech-stack">`.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx

📚 Learning: 2026-03-10T10:37:47.033Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-asana.mdx:15-15
Timestamp: 2026-03-10T10:37:47.033Z
Learning: In src/components/templates/agent-connectors/**/*.mdx, it is acceptable to reuse a single shared redirect URI screenshot (use-own-credentials-redirect-uri.png) across multiple steps within the same connector file, even if different UIs are shown. Do not flag this reuse as an issue; ensure this behavior is intentional and documented for reviewers.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-10T10:38:27.783Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-confluence.mdx:16-16
Timestamp: 2026-03-10T10:38:27.783Z
Learning: In all MDX templates under src/components/templates/agent-connectors, the pattern uses empty alt text (e.g., ![]()) for redirect URI screenshots like use-own-credentials-redirect-uri.png. This is intentional; reviews should not flag missing alt text for these images in this directory.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-12T16:26:39.422Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-bigquery.mdx:18-22
Timestamp: 2026-03-12T16:26:39.422Z
Learning: In agent-connectors MDX templates, it is acceptable to reuse shared Google OAuth screenshots stored under `@/assets/docs/agent-connectors/gmail/` (e.g., oauth-web-app.png, add-redirect-uri.png) across different Google-service connector templates (e.g., _setup-bigquery.mdx, _setup-google-ads.mdx). Do not flag cross-connector image path reuse within Google service connectors as an issue. This guideline applies to all files in this directory.

Applied to files:

src/components/templates/agent-connectors/_usage-exa.mdx
src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-12T16:29:16.422Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-onenote.mdx:12-12
Timestamp: 2026-03-12T16:29:16.422Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using "Azure Active Directory" instead of the rebranded "Microsoft Entra ID" is acceptable and intentional. Do not flag "Azure Active Directory" as outdated branding in these agent-connector setup template files.

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-03-13T03:44:23.786Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:23.786Z
Learning: In src/content/docs/reference/agent-connectors/*.mdx files, small raw HTML <div> blocks used for the connector header grid layout (e.g., a 5-column grid with description and logo) are considered readable without a justification comment. Do not flag the absence of a justification comment on these simple connector-header div blocks in agent-connector reference pages.

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-03-10T10:38:36.402Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-clickup.mdx:17-17
Timestamp: 2026-03-10T10:38:36.402Z
Learning: In `src/components/templates/agent-connectors/_setup-*.mdx` template files, empty alt text `![]()` is the established pattern for redirect URI screenshot images. Do not flag missing alt text on `![]()` markdown image syntax in these agent connector setup template files.

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-03-03T10:47:47.162Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-03T10:47:47.162Z
Learning: Applies to src/content/docs/**/*.{md,mdx} : Proactively address common setup and configuration problems. Keep code examples simple, self-contained, and exportable.

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Use 'collapse={lines}' to hide imports, setup, and boilerplate code in code blocks

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Group related imports together in MDX files

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Import components at the top of MDX files

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Import components at the top of MDX files with consistent import paths using `@/` prefix

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Group related imports together at the top of MDX files

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Use CardGrid, Card, and LinkCard components for hubs and navigation pages in MDX documentation

Applied to files:

src/components/templates/agent-connectors/index.ts

📚 Learning: 2026-03-12T16:28:37.168Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:37.168Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, external links should not be flagged for missing target="_blank" and rel="noopener". Plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) is acceptable and intentional in these agent-connector setup templates, following the established pattern across all connector templates in this directory.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Use Steps component for sequential instructions in MDX documentation

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-12T16:29:08.626Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-onenote.mdx:12-12
Timestamp: 2026-03-12T16:29:08.626Z
Learning: In files matching src/components/templates/agent-connectors/_setup-*.mdx, permit and reflect the branding 'Azure Active Directory' (AAD) as intentional. Do not flag or update these agent-connectors setup templates for references to 'Microsoft Entra ID'. This exception applies only to these setup template files; maintain standard branding elsewhere according to project guidelines.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-10T10:38:30.012Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-clickup.mdx:17-17
Timestamp: 2026-03-10T10:38:30.012Z
Learning: In the repository's agent-connectors setup template files (src/components/templates/agent-connectors/_setup-*.mdx), the pattern for redirect URI screenshot images is to use empty alt text (![]()). Do not flag missing alt text for these specific Markdown image syntaxes in the agent connector setup template files. This guidance applies only to files matching this setup-*.mdx naming pattern; other templates should continue to enforce standard alt text practices.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

🪛 LanguageTool

src/content/docs/reference/agent-connectors/exa.mdx

[uncategorized] ~52-~52: The official name of this software platform is spelled with a capital “H”.
Context: ...e: company, research paper, news, github, tweet, personal site, pdf, `lin...

(GITHUB)

[uncategorized] ~52-~52: The name of this social business platform is spelled with a capital “I”.
Context: ...thub, tweet, personal site, pdf, linkedin profile| |include_domains` | array ...

(LINKEDIN)

[uncategorized] ~62-~62: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...contents.text` | boolean | No | Include full page text in each result (costs 1 extra cred...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

[uncategorized] ~121-~121: The name of this social business platform is spelled with a capital “I”.
Context: ...estrict results to these domains (e.g., ["linkedin.com", "crunchbase.com"]) |

(LINKEDIN)

🔇 Additional comments (4)

src/components/templates/agent-connectors/_usage-exa.mdx (1)

3-38: Looks good for a connector usage template.

The flow is clear: proxy call path, SDK usage, and API-key auth behavior are documented in a practical order.

src/components/templates/agent-connectors/_setup-exa.mdx (1)

5-61: Strong setup flow and good production/testing split.

The sequence and decision points (dashboard vs API, plus rate-limit note) are clear and actionable.

src/components/templates/agent-connectors/index.ts (1)

8-8: Export additions are correct and consistent.

Both new Exa section exports align with the file naming and existing index pattern.

Also applies to: 49-49

src/content/docs/reference/agent-connectors/exa.mdx (1)

20-121: Reference page structure is solid and consistent with connector docs.

The setup/usage composition and per-tool parameter tables are clear and easy to navigate.

netlify · 2026-03-15T16:22:31Z

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	`5c6125d`
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/69b786a8a558b40008f1958e
😎 Deploy Preview	https://deploy-preview-498--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Add two missing Exa tools to the connector reference: - exa_find_similar: find semantically similar pages to a given URL - exa_get_contents: retrieve enriched content for specific URLs without searching Also update setup credits note and page description to reflect new tools.

coderabbitai

♻️ Duplicate comments (1)

src/components/templates/agent-connectors/_setup-exa.mdx (1)

45-49: ⚠️ Potential issue | 🟠 Major

Avoid hard-coded API key values in the SDK example.

Line 48 hard-codes an API key placeholder in a production-oriented snippet. Read the key from runtime config/env and pass the variable instead.

🔐 Suggested fix

        ```python
+       import os
+
+       exa_api_key = os.getenv("EXA_API_KEY")
+       if not exa_api_key:
+           raise ValueError("Set EXA_API_KEY before calling upsert_connected_account")
+
        scalekit_client.actions.upsert_connected_account(
            connection_name="exa",
            identifier="user_123",       # your user's unique ID
-           credentials={"api_key": "your-exa-api-key"}
+           credentials={"api_key": exa_api_key}
        )
        ```

As per coding guidelines, "Never teach bad habits or insecure patterns; never hard-code secrets or API keys in examples."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/components/templates/agent-connectors/_setup-exa.mdx` around lines 45 -
49, Replace the hard-coded API key in the
scalekit_client.actions.upsert_connected_account call by reading it from runtime
config/environment (e.g., load EXA_API_KEY into a variable like exa_api_key) and
pass that variable in credentials; before calling upsert_connected_account
validate exa_api_key and raise/throw a clear error (e.g., ValueError) if it's
missing so the snippet doesn't teach hard-coding secrets.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@src/components/templates/agent-connectors/_setup-exa.mdx`:
- Around line 45-49: Replace the hard-coded API key in the
scalekit_client.actions.upsert_connected_account call by reading it from runtime
config/environment (e.g., load EXA_API_KEY into a variable like exa_api_key) and
pass that variable in credentials; before calling upsert_connected_account
validate exa_api_key and raise/throw a clear error (e.g., ValueError) if it's
missing so the snippet doesn't teach hard-coding secrets.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 55d66561-fae8-409a-8010-c09940755103

📥 Commits

Reviewing files that changed from the base of the PR and between baa86b9 and 5c6125d.

📒 Files selected for processing (2)

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

📜 Review details

🧰 Additional context used

📓 Path-based instructions (4)

**/*.mdx

📄 CodeRabbit inference engine (.cursorrules)

**/*.mdx: Use clear, descriptive titles that explain the purpose of the document
Include comprehensive descriptions in frontmatter metadata
Organize content with logical heading hierarchy (H2, H3, H4)
Use tableOfContents property in frontmatter when content has multiple sections
Set appropriate sidebar labels for navigation in frontmatter
Use direct instruction writing style with phrases like 'This guide shows you how to...' and 'Create an authorization URL to...'
Use second person perspective ('your application', 'you receive', 'you must') in documentation
Keep sentences concise, aiming for under 25 words per sentence
Explain the 'why' in documentation with phrases like 'This prevents CSRF attacks by...' or 'Use this to validate that...'
Use action verbs in section headings: 'Store session tokens securely', 'Validate the state parameter', 'Exchange authorization code for tokens'
Use present tense for descriptions: 'Scalekit handles the complex authentication flow', 'The SDK provides methods to refresh tokens'
Use future tense for results: 'This will redirect users to...', 'You'll receive a JWT containing...', 'Scalekit returns an authorization code'
Use transition phrases between sections: 'After the user authenticates...', 'Once the state is validated...', 'Let's take a look at how to...'
Write 1-3 opening paragraphs that explain what users will accomplish, provide context about when/why, preview key concepts, and use direct instructional language
Begin introduction sections with a clear statement of what the guide covers and explain the problem being solved
Use collapsible sections in introduction for sequence diagrams, video demonstrations, data models, and JSON examples with appropriate icons
Use numbered format within Steps component: 1. ## Title with all step content indented with exactly 3 spaces
Use action-oriented headings in step-by-step guides within Steps components
Include code examples in all 4 languages (Node.js, Python, Go, Java) within Steps co...

Files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

⚙️ CodeRabbit configuration file

**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:

Frontmatter

title MUST be ≤ 60 characters and clearly state what the page does.

description MUST be ≤ 160 characters, action-oriented, unique per page.

sidebar.label MUST be present and ≤ 30 characters.

sidebar.order MUST be set on every page that lives inside a section
with siblings, to enforce the journey order in sidebar.config.ts.

Flag any missing prev / next links on pages that are clearly
part of a sequential flow (e.g., quickstart → implement-login →
complete-login → manage-session → logout).

Voice & Style (CLAUDE.md standards)

Voice: confident, direct, collaborative, instructional.

Person: second person only ("you", "your application"). Reject "we",
"our", "the developer", "the user".

Tense: present tense for descriptions; imperative mood for instructions.

Flag weasel words: "simply", "just", "easy", "straightforward",
"obviously", "of course", "note that".

Flag passive voice constructions where active voice is clearer.

Headings must be sentence case, not Title Case (except proper nouns).

No heading should end with a colon or period.

Content structure

How-to guides MUST contain numbered <Steps> (Starlight component).

Concept pages MUST NOT contain numbered steps — concepts explain, not instruct.

API reference pages MUST list parameters in a table with Name / Type /
Required / Description columns.

Every page MUST end with a clear "what's next" signal — either a
next: frontmatter link, a <LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.

Code examples

ALL code examples that show SDK usage MUST include all four language
tabs: Node.js, Python, Go, Java — using <Tabs syncKey="tech-stack">.

SDK variable names are STRICTLY: scalekit (Node.js),
scalekit_client (Python), scalekitClient (Go), ...

Files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

**/*.{yml,yaml,md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/browsecentral-labels.mdc)

**/*.{yml,yaml,md,mdx}: BrowseCentral labels should be maximum 3-5 words - keep concise but add context when needed
BrowseCentral labels should be action-oriented - start with verbs when possible
BrowseCentral labels should be specific and clear - add context when simple labels are ambiguous
BrowseCentral labels should be outcome-focused - describe what users accomplish and the context
BrowseCentral labels should use 'Action + Object' pattern (e.g., 'Invite users', 'Restrict sign-up', 'Set up SCIM')
BrowseCentral labels should use feature names (e.g., 'Enterprise SSO', 'Passwordless quickstart')
BrowseCentral labels should describe task completion (e.g., 'Run migrations', 'Migrate auth', 'Merge identities')
BrowseCentral labels should include specific context when needed (e.g., 'Configure Scalekit MCP server', 'Validate incoming API requests')
BrowseCentral labels should use integration context when applicable (e.g., 'Build MCP auth with your existing auth system')
BrowseCentral labels should avoid instructional prefixes: 'How to', 'Guide to', 'Implement', 'Configure', 'Learn', 'Understand'
BrowseCentral labels should avoid verbose phrases: 'Step-by-step guide', 'Complete tutorial', 'Detailed documentation'
BrowseCentral labels should avoid weak verbs: 'Enable', 'Allow', 'Provide', 'Support'

Files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

**/*.{md,mdx}

📄 CodeRabbit inference engine (.cursor/rules/deno-docs-style.mdc)

**/*.{md,mdx}: Use sentence case for all titles and headings in MD/MDX documentation
Keep page titles short and descriptive (3–7 words when possible) in MD/MDX documentation
Use outcome-focused headings that describe results, not categories (e.g., 'Run a script' not 'Scripts')
Avoid gerunds in headings when an imperative works - prefer 'Configure proxies' over 'Configuring proxies'
Keep sidebar labels concise (1–3 words), use sentence case, and focus on outcomes or objects
Use sentence case in sidebar labels without punctuation
Set frontmatter title in sentence case with a clear outcome; description in one sentence (≤160 chars); sidebar.label as shorter form of title; enable tableOfContents on longer pages
Start documentation pages with a one-paragraph overview explaining what the page covers and when to use it
Present the primary use case (80% path) first in documentation, with edge cases later
Use numbered steps for task-focused sections in documentation, with each step beginning with a verb
Break up long documentation sections with subheadings every 3–6 paragraphs
Use asides for important notes, tips, cautions, and references in documentation
Provide runnable, minimal code examples that work as-is in documentation
Prefer CLI-first examples and show file layout when helpful in documentation
Label code blocks with titles for context (e.g., 'Terminal', 'main.ts') in documentation
Keep code block annotations brief and purposeful - annotate only what matters
Use consistent variable and file names across a documentation page
Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')
Prefer relative links for internal documentation pages and include anchors for section references
Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints
Use backticks for code, file names, CLI flags, and endpoints in documentation
Use lists for options and features in documentation; tables only when comparisons are cleare...

Files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

src/content/docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (CLAUDE.md)

src/content/docs/**/*.{md,mdx}: Product-based documentation (MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, Modular SSO) MUST follow a journey-focused approach. Each product represents a developer's journey toward implementing authentication in their projects.
Proactively address common setup and configuration problems. Keep code examples simple, self-contained, and exportable.
Use imperative for procedures: 'Install', 'Create', 'Run', 'Configure', 'Test'. Front-load the action and start sentences with the verb or key concept.
Explain why when useful. Briefly justify non-obvious steps. Prefer examples over theory; show the common path first and link to details.
Every page MUST include frontmatter with at least: title (≤60 characters), description (≤160 characters), and sidebar.label (1-3 words). Use sidebar.order only when navigation ordering matters. Use prev/next for sequential guides; use seeAlso for related guides. Enable tableOfContents for longer pages with multiple major sections.
Opening paragraphs (1-3) MUST state what users will accomplish, when/why they need it, and preview the workflow using direct instructional language
The Steps component requires a single continuous ordered list. Steps must start at column 0 with no leading spaces. Continuation content (images, text) must be indented with exactly 3 spaces. Sub-bullet lists use 3 spaces with no blank line before bullets. No blank line immediately after Steps opening tag.
Documentation must be organized into logical sections (FSA, SSO, Directory/SCIM, Connect, M2M, Guides, Reference) with proper sidebar configuration and navigation structure

Files:

src/content/docs/reference/agent-connectors/exa.mdx

🧠 Learnings (34)

📓 Common learnings

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 0
File: :0-0
Timestamp: 2026-03-13T04:24:59.653Z
Learning: In scalekit-inc/developer-docs, for PRs focused on tooling and templatizing (e.g., extracting usage sections into reusable MDX templates and updating sync scripts), review comments about .mdx file content quality (casing, unused imports, import consolidation, endpoint descriptions, etc.) are considered out of scope and should be resolved without blocking the PR.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:55.583Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, the parameter tables (showing tool properties) are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Any table format corrections must be made in the generation script, not by manually editing the generated MDX files. The script should be updated to output the required "Name | Type | Required | Description" four-column table format per coding guidelines.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:23.786Z
Learning: In src/content/docs/reference/agent-connectors/*.mdx files, small raw HTML <div> blocks used for the connector header grid layout (e.g., a 5-column grid with description and logo) are considered readable without a justification comment. Do not flag the absence of a justification comment on these simple connector-header div blocks in agent-connector reference pages.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:27.672Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, do not enforce the 160-character description limit. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may have longer descriptions from the source data.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:46.903Z
Learning: For auto-generated agent connector documentation pages in src/content/docs/reference/agent-connectors/, the "what's next" signal requirement (next: frontmatter link, <LinkCard>, or concluding paragraph) does not apply. These are reference pages generated by scripts/sync-agent-connectors.js and serve as lookup resources rather than sequential guides.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:56.400Z
Learning: For Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), currently only Python SDK support is available for Agent Actions/Agent Connectors. Do not require or enforce the multi-language SDK code examples (Node.js, Python, Go, Java) guideline for these connector docs until SDK support is ready in other languages. The Node.js, Go, and Java examples can be added once the respective SDKs support Agent Actions features.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:37.207Z
Learning: In src/content/docs/reference/agent-connectors/** MDX files, tool headings (e.g., `googlesheets_create_spreadsheet`, `googlesheets_get_values`) intentionally use H2 (##) instead of H3 to ensure they appear in the table of contents for easier navigation. This is a deliberate UX choice for agent connector reference pages and should not be flagged as a hierarchy issue.

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:51.377Z
Learning: In src/content/docs/reference/agent-connectors/**/*.mdx files, sidebar.label frontmatter is not required because the sidebar configuration references the agent-connectors directory for auto-generation. Navigation ordering and grouping are managed centrally in the sidebar configuration file.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs generally), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication connection type documentation in Agent Auth connection-type sections.

Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 487
File: src/content/docs/agent-auth/connections.mdx:0-0
Timestamp: 2026-03-12T05:02:13.454Z
Learning: In `src/content/docs/agent-auth/connections.mdx` (and Agent Auth docs in general), custom authentication (username/password/bearer-token flows) is intentionally out of scope for the current Agent Auth release. Do not flag the absence of custom authentication documentation in Agent Auth connection-type sections.

📚 Learning: 2026-03-12T16:28:37.168Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:37.168Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, external links should not be flagged for missing target="_blank" and rel="noopener". Plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) is acceptable and intentional in these agent-connector setup templates, following the established pattern across all connector templates in this directory.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:22:55.583Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:55.583Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, the parameter tables (showing tool properties) are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Any table format corrections must be made in the generation script, not by manually editing the generated MDX files. The script should be updated to output the required "Name | Type | Required | Description" four-column table format per coding guidelines.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include configuration comments in code examples: '// Get the signing secret from Scalekit dashboard > Interceptors tab'

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:48:11.566Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Use Steps component for sequential instructions in MDX documentation

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:23:27.672Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:27.672Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, do not enforce the 160-character description limit. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may have longer descriptions from the source data.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include use case comments explaining scenarios in code examples: '// Use case: Provision a workspace after a sales-assisted onboarding'

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:21:37.207Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:37.207Z
Learning: In src/content/docs/reference/agent-connectors/** MDX files, tool headings (e.g., `googlesheets_create_spreadsheet`, `googlesheets_get_values`) intentionally use H2 (##) instead of H3 to ensure they appear in the table of contents for easier navigation. This is a deliberate UX choice for agent connector reference pages and should not be flagged as a hierarchy issue.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-10T10:37:47.033Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-asana.mdx:15-15
Timestamp: 2026-03-10T10:37:47.033Z
Learning: In src/components/templates/agent-connectors/**/*.mdx, it is acceptable to reuse a single shared redirect URI screenshot (use-own-credentials-redirect-uri.png) across multiple steps within the same connector file, even if different UIs are shown. Do not flag this reuse as an issue; ensure this behavior is intentional and documented for reviewers.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Test MDX documentation locally before committing to catch parsing and Steps component indentation errors

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-13T03:44:23.786Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:23.786Z
Learning: In src/content/docs/reference/agent-connectors/*.mdx files, small raw HTML <div> blocks used for the connector header grid layout (e.g., a 5-column grid with description and logo) are considered readable without a justification comment. Do not flag the absence of a justification comment on these simple connector-header div blocks in agent-connector reference pages.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-25T03:34:41.147Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:31-31
Timestamp: 2026-02-25T03:34:41.147Z
Learning: In MDX files, import { Code } from 'astrojs/starlight/components' only if the MDX content actually uses the <Code> component. If the file uses only fenced code blocks (```), the import is not required. Apply this guideline to all MDX files (e.g., src/content/docs/**/*.mdx) to avoid unnecessary imports and reduce bundle size.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T18:41:00.639Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 446
File: src/content/docs/authenticate/m2m/api-auth-quickstart.mdx:78-78
Timestamp: 2026-02-25T18:41:00.639Z
Learning: Preserve full URLs inside code comments in MDX code blocks (bash/python/js) when the URLs are part of copyable examples. Do not flag these in code examples. Use relative paths in prose and hyperlinks within MDX; only enforce relative paths for markdown prose links, not for URLs inside code comments.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx
src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-10T10:38:27.783Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-confluence.mdx:16-16
Timestamp: 2026-03-10T10:38:27.783Z
Learning: In all MDX templates under src/components/templates/agent-connectors, the pattern uses empty alt text (e.g., ![]()) for redirect URI screenshots like use-own-credentials-redirect-uri.png. This is intentional; reviews should not flag missing alt text for these images in this directory.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-12T16:26:39.422Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-bigquery.mdx:18-22
Timestamp: 2026-03-12T16:26:39.422Z
Learning: In agent-connectors MDX templates, it is acceptable to reuse shared Google OAuth screenshots stored under `@/assets/docs/agent-connectors/gmail/` (e.g., oauth-web-app.png, add-redirect-uri.png) across different Google-service connector templates (e.g., _setup-bigquery.mdx, _setup-google-ads.mdx). Do not flag cross-connector image path reuse within Google service connectors as an issue. This guideline applies to all files in this directory.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-10T10:38:30.012Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 475
File: src/components/templates/agent-connectors/_setup-clickup.mdx:17-17
Timestamp: 2026-03-10T10:38:30.012Z
Learning: In the repository's agent-connectors setup template files (src/components/templates/agent-connectors/_setup-*.mdx), the pattern for redirect URI screenshot images is to use empty alt text (![]()). Do not flag missing alt text for these specific Markdown image syntaxes in the agent connector setup template files. This guidance applies only to files matching this setup-*.mdx naming pattern; other templates should continue to enforce standard alt text practices.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-03-12T16:29:08.626Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-onenote.mdx:12-12
Timestamp: 2026-03-12T16:29:08.626Z
Learning: In files matching src/components/templates/agent-connectors/_setup-*.mdx, permit and reflect the branding 'Azure Active Directory' (AAD) as intentional. Do not flag or update these agent-connectors setup templates for references to 'Microsoft Entra ID'. This exception applies only to these setup template files; maintain standard branding elsewhere according to project guidelines.

Applied to files:

src/components/templates/agent-connectors/_setup-exa.mdx

📚 Learning: 2026-02-26T07:22:49.128Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:23:24.179Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-13T03:44:16.883Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/youtube.mdx:19-26
Timestamp: 2026-03-13T03:44:16.883Z
Learning: In MDX files under src/content/docs/reference/agent-connectors, specifically simple connector-header div blocks used for the header grid layout (e.g., a 5-column grid with description and logo), treat the absence of a justification comment as acceptable/readable. Do not flag or require a justification comment for these simple header div blocks in agent-connector reference pages.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:21:32.951Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:18:41.518Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-26T07:20:42.107Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-12T16:28:42.817Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 483
File: src/components/templates/agent-connectors/_setup-zendesk.mdx:20-20
Timestamp: 2026-03-12T16:28:42.817Z
Learning: In src/components/templates/agent-connectors/_setup-*.mdx files, using plain Markdown link syntax (e.g., [Scalekit dashboard](https://app.scalekit.com)) for external links is acceptable and intentional. Do not flag the absence of target="_blank" and rel="noopener" attributes in these agent-connector setup template files. This follows the established pattern across all connector templates in this directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-03T13:35:47.638Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 455
File: src/content/docs/reference/agent-connectors/asana.mdx:94-173
Timestamp: 2026-03-03T13:35:47.638Z
Learning: In Agent Connectors documentation (src/content/docs/reference/agent-connectors/**/*.mdx), only Python SDK examples for Agent Actions/Agent Connectors should be required for now. Do not enforce or require multi-language SDK code examples (Node.js, Python, Go, Java) until the respective SDKs support Agent Actions. Once supported, you can add and require other languages in those docs. This guideline applies to all files under the agent-connectors documentation path.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-01-13T12:46:55.260Z

Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include comprehensive descriptions in frontmatter metadata

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-01-30T18:18:50.883Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-04T12:47:16.544Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T08:57:12.201Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-02-25T13:04:27.491Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-05T11:29:08.125Z

Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 463
File: src/content/docs/agent-auth/providers.mdx:35-73
Timestamp: 2026-03-05T11:29:08.125Z
Learning: In src/content/docs/agent-auth/providers.mdx, the Card components intentionally use icon=" " (a space) to render consistent colored boxes since some Starlight icon names resolve to icons and others do not. Do not flag icon=" " as a placeholder issue for this file; treat this as a deliberate UX choice specific to this MDX page and avoid raising a placeholder-icon warning here.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-09T07:27:56.794Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 469
File: src/content/docs/guides/integrations/scim-integrations/azure-scim.mdx:95-107
Timestamp: 2026-03-09T07:27:56.794Z
Learning: Do not enforce the 3-space indentation rule for Steps component content as a hard style rule in MDX files under src/content/docs/**/*.mdx. Only flag/rectify it if it causes visible rendering problems in the UI. Otherwise, allow current formatting; apply this rule only when rendering issues are observed and document any fixes.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-09T07:32:38.426Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 467
File: src/content/docs/sso/guides/sso-user-attributes.mdx:108-148
Timestamp: 2026-03-09T07:32:38.426Z
Learning: In MDX code samples under src/content/docs (and similar conceptual snippets in scalekit-inc/developer-docs), when an example's sole purpose is to show how to access a specific value (e.g., reading JWT claims after token validation), omit error/non-happy-path handling to keep the snippet focused. Do not flag the absence of error paths in narrowly scoped conceptual snippets.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

📚 Learning: 2026-03-13T03:51:40.660Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 489
File: src/content/docs/reference/agent-connectors/attio.mdx:24-24
Timestamp: 2026-03-13T03:51:40.660Z
Learning: In src/content/docs/reference/agent-connectors/**, enforce using CDN URLs for provider-icon logos with the host https://cdn.scalekit.com/sk-connect/assets/provider-icons/ (e.g., https://cdn.scalekit.com/sk-connect/assets/provider-icons/attio.svg). The host should be cdn.scalekit.com (not cdn.scalekit.cloud). Do not flag or modify image src attributes that already use cdn.scalekit.com for provider icons within this directory.

Applied to files:

src/content/docs/reference/agent-connectors/exa.mdx

🪛 LanguageTool

src/content/docs/reference/agent-connectors/exa.mdx

[uncategorized] ~52-~52: The official name of this software platform is spelled with a capital “H”.
Context: ...e: company, research paper, news, github, tweet, personal site, pdf, `lin...

(GITHUB)

[uncategorized] ~52-~52: The name of this social business platform is spelled with a capital “I”.
Context: ...thub, tweet, personal site, pdf, linkedin profile| |include_domains` | array ...

(LINKEDIN)

[uncategorized] ~62-~62: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...contents.text` | boolean | No | Include full page text in each result (costs 1 extra cred...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

[uncategorized] ~82-~82: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...contents.text` | boolean | No | Include full page text in each result (costs 1 extra cred...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

(EN_COMPOUND_ADJECTIVE_INTERNAL)

[uncategorized] ~165-~165: The name of this social business platform is spelled with a capital “I”.
Context: ...estrict results to these domains (e.g., ["linkedin.com", "crunchbase.com"]) |

(LINKEDIN)

🔇 Additional comments (1)

src/content/docs/reference/agent-connectors/exa.mdx (1)

47-165: Reference section structure looks solid.

Tool sections and parameter tables are consistently structured and match the expected connector reference format.

Pranesh-Raghu added 2 commits March 13, 2026 15:51

exa

61f1071

Pranesh-Raghu requested review from amitash1912, ravibits and saif-at-scalekit as code owners March 15, 2026 14:02

Pranesh-Raghu requested a review from Avinash-Kamath March 15, 2026 14:03

coderabbitai Bot requested changes Mar 15, 2026

View reviewed changes

Comment thread src/components/templates/agent-connectors/_setup-exa.mdx

coderabbitai Bot reviewed Mar 16, 2026

View reviewed changes

coderabbitai Bot approved these changes Mar 16, 2026

View reviewed changes

Pranesh-Raghu merged commit a6aef16 into scalekit-inc:main Mar 17, 2026
4 checks passed

coderabbitai Bot mentioned this pull request Mar 30, 2026

Figma agent connector and Tools #554

Merged

5 tasks

This was referenced Apr 9, 2026

Add Parallel AI Task MCP connector docs #579

Merged

Supadata agent connector setup guide #603

Merged

This was referenced Apr 17, 2026

chore(agent-connectors): sync tools and providers from API #617

Merged

Add Tableau connector docs #626

Merged

coderabbitai Bot mentioned this pull request Apr 25, 2026

docs(agentkit): add HeyReach agent connector #633

Merged

5 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Exa connector and tools#498

Exa connector and tools#498
Pranesh-Raghu merged 3 commits into
scalekit-inc:mainfrom
Pranesh-Raghu:Exa-Connector-and-Tools

Pranesh-Raghu commented Mar 15, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Mar 15, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

netlify Bot commented Mar 15, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Pranesh-Raghu commented Mar 15, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

netlify Bot commented Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for scalekit-starlight ready!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Frontmatter

Voice & Style (CLAUDE.md standards)

Content structure

Code examples

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Pranesh-Raghu commented Mar 15, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Mar 15, 2026 •

edited

Loading

netlify Bot commented Mar 15, 2026 •

edited

Loading