Add Tableau connector docs#626
Merged
Merged
Conversation
Pranesh-Raghu
requested review from
amitash1912,
ravibits and
saif-at-scalekit
as code owners
Contributor
|
Caution Review failedPull request was closed or merged during review Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds a new Tableau agent connector: two MDX docs (setup, usage), a main connector doc, exports for the new MDX sections, and a comprehensive Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Agent
participant Scalekit as "Scalekit Proxy"
participant Connector as "Tableau Connector (tools)"
participant Tableau as "Tableau REST API"
Note over Agent,Tableau: PAT → session → proxied requests
Agent->>Scalekit: createConnectedAccount(PAT, site_content_url)
Scalekit->>Connector: store PAT, request session exchange
Connector->>Tableau: POST /auth/signin (uses PAT)
Tableau-->>Connector: returns X-Tableau-Auth (session token) + site_id
Connector-->>Scalekit: persist session token and expiry
Agent->>Scalekit: invoke tool or actions.request(...) (proxy path)
Scalekit->>Connector: resolve tool, inject X-Tableau-Auth, forward proxied request
Connector->>Tableau: proxied API call using session token
Tableau-->>Connector: API response (data or binary)
Connector-->>Scalekit: return response
Scalekit-->>Agent: response delivered
Note over Connector,Tableau: Connector refreshes session token automatically before expiry
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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-tableau.mdx`:
- Around line 183-209: The function refreshTableauToken references domain but
never declares it; declare const domain = process.env.TABLEAU_DOMAIN at the top
of refreshTableauToken (and validate it: throw or return an error if missing) so
the fetch call to `https://${domain}/api/3.28/auth/signin` has a defined value,
and ensure the same domain value is used when calling
scalekit.actions.upsertConnectedAccount to persist credentials; include a clear
error message like 'TABLEAU_DOMAIN is required' for the validation.
In `@src/content/docs/agentkit/connectors/tableau.mdx`:
- Around line 24-28: The docs claim “add, update, and remove users and groups”
but the connector only implements addUser, removeUser, createGroup, addGroup,
and removeGroup in src/data/agent-connectors/tableau.ts; either remove the
“update” wording from the Tableau connector docs in
src/content/docs/agentkit/connectors/tableau.mdx or implement and export
updateUser/updateGroup handlers in tableau.ts (and wire them into the connector
surface) so the documentation matches the available symbols.
- Around line 32-37: Update the Tableau auth overview to reflect the PAT-only
connector contract: state that users sign in with a Personal Access Token (PAT)
which returns a session token injected as the X-Tableau-Auth header (referencing
tableau_auth_signin), remove mention of username/password or generic sign-in,
and keep the token expiry described as environment-specific (120 minutes for
Tableau Cloud, 240 minutes for Tableau Server) so it matches the behavior
implemented in the connector code.
In `@src/data/agent-connectors/tableau.ts`:
- Around line 1124-1142: The params for the VizQL query currently declare
'fields', 'filters', and 'sort' with type 'string' but should be structured
arrays; update each param (the entries with name 'fields', 'filters', and 'sort'
in the tableau connector params) to use ParamType 'array' and supply an
appropriate "items" schema (object with expected properties such as
fieldCaption, function for fields; field, filterType, values for filters; field,
sortDirection for sort) so the generated tool contract exposes structured
objects rather than serialized JSON; keep required flags and descriptions, and
reuse any existing shared types/schemas if available.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 23da6f4f-824d-4482-8010-716eea008779
📒 Files selected for processing (5)
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.mdxsrc/data/agent-connectors/tableau.ts
📜 Review details
🧰 Additional context used
📓 Path-based instructions (11)
**/*.{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/data/agent-connectors/tableau.tssrc/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/data/agent-connectors/tableau.tssrc/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/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/index.ts
**/*.{js,ts,tsx,py,go,java}
📄 CodeRabbit inference engine (AGENTS.md)
Use exact SDK variable names: Node.js:
scalekit, Python:scalekit_client, Go:scalekitClient, Java:scalekitClient
Files:
src/data/agent-connectors/tableau.tssrc/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/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/index.ts
**/*.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. ## Titlewith 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-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
⚙️ CodeRabbit configuration file
**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:Frontmatter
titleMUST be ≤ 60 characters and clearly state what the page does.descriptionMUST be ≤ 160 characters, action-oriented, unique per page.sidebar.labelMUST be present and ≤ 30 characters.sidebar.orderMUST 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/nextlinks 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
- Journey how-to guides MUST contain numbered
<Steps>(Starlight
component). This does NOT apply tosrc/content/docs/cookbooks/**
(blog-style recipes — optional<Steps>,<Tabs>after</Steps>OK;
see cookbookspath_instructions).- 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...
Files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
src/content/docs/**/*.mdx
📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)
src/content/docs/**/*.mdx: In MDX documentation files,<Steps>must contain one continuous ordered list. Wrap<Steps>around a normal Markdown ordered list such as1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the1. ##,2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images,<Tabs>,<TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside<Steps>. If the content is mostly<Tabs>or other JSX-heavy blocks, use normal section headings instead of<Steps>
In MDX documentation files, when<Tabs>is used inside a step, keep<Tabs>,<TabItem>,</TabItem>, and</Tabs>consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside</Steps>
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
src/content/docs/**/*.{md,mdx}: Every documentation page must include frontmatter with at least:title(≤60 chars),description(≤160 chars), andsidebar.label(1-3 words)
Use H2 for major sections, H3 for subsections, and H4 only inside<Steps>; never use H1 in body content and avoid nesting beyond H4
Use numbered lists only inside<Steps>for ordered procedures; use bulleted lists for unordered information
Use bold for first mention of important terms, UI elements, and dashboard paths; use inline code for technical identifiers (variables, functions, endpoints, scopes, environment variables, file paths, placeholders)
The<Steps>component requires a single continuous ordered list with proper indentation: steps at column 0, continuation content indented with exactly 3 spaces
Use<Aside>component with atitleattribute for cautions, tips, and notes
Use<Badge>component to indicate parameter requirements in tables and inline text
Use<details>blocks at the end of pages for FAQs, common scenarios, and troubleshooting
Split content into clear sections with descriptive, sentence-style titles; include a table of contents for documents with multiple sections; keep paragraphs short and isolate critical points in their own short paragraphs
Begin sections and paragraphs with standalone topic sentences that preview content; put topic words at the beginning to support fast skimming; put key takeaways and results at the top of documents
Use bullets and tables generously to structure information; bold important text to highlight key concepts and decisions
Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns like 'this' or 'that' when the referent is not explicit
Maintain strict consistency in terminology, formatting, and style; do not presume the reader's state of mind or intentions; use direct, instructional language
Write more simply than you think you need to; optimize for readers new to the do...
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/agentkit/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
Agentkit code examples live in the external repo scalekit-developers/agent-auth-examples organized as
javascript/frameworks/<framework>andpython/frameworks/<framework>; verify docs snippets match current implementations in that repo
Files:
src/content/docs/agentkit/connectors/tableau.mdx
🧠 Learnings (46)
📓 Common learnings
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: 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/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.
📚 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/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-04-22T09:58:57.649Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227
Timestamp: 2026-04-22T09:58:57.649Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews.
Applied to files:
src/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 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-tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-04-13T10:43:05.628Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 590
File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83
Timestamp: 2026-04-13T10:43:05.628Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.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-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-04-20T17:03:02.786Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 619
File: src/components/templates/agent-connectors/_usage-posthogmcp.mdx:82-82
Timestamp: 2026-04-20T17:03:02.786Z
Learning: In `src/components/templates/agent-connectors/_usage-posthogmcp.mdx`, the trailing `## Scalekit Tools` heading is intentionally omitted. The parent connector page (`src/content/docs/agentkit/connectors/posthogmcp.mdx`) renders the tool list separately via the `ToolList` component and the imported `tools` dataset, so the structural anchor heading used by other `_usage-*.mdx` templates is not needed here. Do not flag the missing `## Scalekit Tools` heading in this file.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/index.tssrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.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-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/components/templates/agent-connectors/index.tssrc/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-03-10T10:37:49.873Z
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:49.873Z
Learning: In `src/components/templates/agent-connectors/`, all connector setup MDX files (e.g., _setup-asana.mdx, _setup-clickup.mdx, _setup-confluence.mdx, _setup-googlecalendar.mdx, _setup-intercom.mdx, _setup-monday.mdx, _setup-notion.mdx, _setup-zoom.mdx) intentionally use a single shared redirect URI screenshot (`use-own-credentials-redirect-uri.png` located under `@/assets/docs/agent-connectors/<connector-name>/`) for all redirect URI-related steps, even when steps show different UIs (e.g., Scalekit dashboard vs. the third-party console). Do not flag reuse of this image across multiple steps within the same connector file as an issue.
Applied to files:
src/components/templates/agent-connectors/index.ts
📚 Learning: 2026-04-20T11:29:40.242Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-20T11:29:40.242Z
Learning: Applies to {src/content/docs/guides/integrations/**/*.{md,mdx},src/components/templates/_*.{ts,tsx,astro}} : Integration guides in `src/content/docs/guides/integrations/` must be kept synchronized with their corresponding index pages and use reusable template components from `src/components/templates/`
Applied to files:
src/components/templates/agent-connectors/index.ts
📚 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/index.ts
📚 Learning: 2026-04-20T11:30:52.410Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-20T11:30:52.410Z
Learning: Applies to **/*.{md,mdx} : Use normal section headings instead of `<Steps>` when content is mostly `<Tabs>`, long JSX blocks, or multiple embedded components
Applied to files:
src/components/templates/agent-connectors/index.ts
📚 Learning: 2026-04-20T11:29:40.242Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-20T11:29:40.242Z
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: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: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 : 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 : 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: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: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/index.ts
📚 Learning: 2026-03-16T21:02:51.181Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/expressive-code.mdc:0-0
Timestamp: 2026-03-16T21:02:51.181Z
Learning: Applies to **/*.mdx : Import `<Code>` from `astrojs/starlight/components` once per file below frontmatter 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 : 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-02-26T07:20:46.903Z
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.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-13T03:51:44.897Z
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.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-17T16:01:50.487Z
Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-13T10:43:03.024Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 590
File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83
Timestamp: 2026-04-13T10:43:03.024Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, keep the trailing `## Scalekit Tools` heading at the end of each template. Do not flag it as empty or as a duplicate heading in future reviews for these files, since it is an intentional structural anchor used by the parent connector reference page to append the tool-list section beneath the proxy API examples.
Applied to files:
src/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-03-25T15:59:47.933Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48
Timestamp: 2026-03-25T15:59:47.933Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, the code snippets are intentionally directional/illustrative and are meant to demonstrate the expected call sequence, not production-ready runnable code. When reviewing these files, do not flag missing `try/except` (Python) or `try/catch` (JS/TS) error handling solely because the snippet omits it—focus on whether the call sequence/pattern is conveyed clearly.
Applied to files:
src/components/templates/agent-connectors/_usage-tableau.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-tableau.mdx
🪛 LanguageTool
src/content/docs/agentkit/connectors/tableau.mdx
[style] ~25-~25: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNGs”.
Context: ...sualizations** — Download dashboards as PNG images, PDF documents, or Excel crosstab files...
(ACRONYM_TAUTOLOGY)
src/components/templates/agent-connectors/_usage-tableau.mdx
[style] ~159-~159: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNG”.
Context: .../TabItem> ### Export a view as PNG image <TabItem...
(ACRONYM_TAUTOLOGY)
✅ Deploy Preview for scalekit-starlight ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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/_usage-tableau.mdx`:
- Line 159: Update the heading text in the agent-connectors Tableau usage doc:
replace the phrase "Export a view as PNG image" with the non-redundant "Export a
view as PNG" (locate the heading string "### Export a view as PNG image" in
_usage-tableau.mdx and edit it accordingly).
In `@src/content/docs/agentkit/connectors/tableau.mdx`:
- Line 25: Update the text under the "Export visualizations" entry that
currently reads "Download dashboards as PNG images, PDF documents, or Excel
crosstab files; download full workbooks as `.twbx` files" to remove the
redundancy by replacing "PNG images" with either "PNGs" or "images" (e.g.,
"Download dashboards as PNGs, PDF documents, or Excel crosstab files; download
full workbooks as `.twbx` files") so the wording is concise and non-redundant.
- Around line 1-13: The frontmatter in the Tableau doc is missing the required
fields; add a short description (<=160 characters) and a sidebar.label (1–3
words) to the existing frontmatter at the top of
src/content/docs/agentkit/connectors/tableau.mdx so it includes both
`description: "<brief summary>"` and `sidebar.label: "<1-3 words>"` alongside
the existing keys (title, tableOfContents, connectorIcon, connectorAuthType,
connectorCategories, head).
In `@src/data/agent-connectors/tableau.ts`:
- Around line 237-322: The tool names are inconsistent: tableau_views_list
(site-wide) vs tableau_list_views (workbook-scoped); rename tableau_list_views
to a consistent identifier such as tableau_workbook_views_list (or
tableau_views_list_by_workbook) and update all occurrences of tableau_list_views
in the codebase (export/registration, docs, tests, any callers) to the new
symbol so agents and LLM tool lookup use the unified naming convention; ensure
the params and descriptions remain unchanged except where you reference the new
function name.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 1cefbf07-2d54-4af6-9b0e-1da9eff1a999
⛔ Files ignored due to path filters (4)
src/assets/docs/agent-connectors/tableau/add-connected-account.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/tableau/add-credentials.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/tableau/create-pat.pngis excluded by!**/*.pngsrc/assets/docs/agent-connectors/tableau/scalekit-search-tableau.pngis excluded by!**/*.png
📒 Files selected for processing (4)
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdxsrc/data/agent-connectors/tableau.ts
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Redirect rules - scalekit-starlight
- GitHub Check: Header rules - scalekit-starlight
- GitHub Check: Pages changed - scalekit-starlight
🧰 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. ## Titlewith 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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
⚙️ CodeRabbit configuration file
**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:Frontmatter
titleMUST be ≤ 60 characters and clearly state what the page does.descriptionMUST be ≤ 160 characters, action-oriented, unique per page.sidebar.labelMUST be present and ≤ 30 characters.sidebar.orderMUST 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/nextlinks 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
- Journey how-to guides MUST contain numbered
<Steps>(Starlight
component). This does NOT apply tosrc/content/docs/cookbooks/**
(blog-style recipes — optional<Steps>,<Tabs>after</Steps>OK;
see cookbookspath_instructions).- 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...
Files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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/data/agent-connectors/tableau.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/data/agent-connectors/tableau.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/data/agent-connectors/tableau.ts
**/*.{js,ts,tsx,py,go,java}
📄 CodeRabbit inference engine (AGENTS.md)
Use exact SDK variable names: Node.js:
scalekit, Python:scalekit_client, Go:scalekitClient, Java:scalekitClient
Files:
src/data/agent-connectors/tableau.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/data/agent-connectors/tableau.ts
src/content/docs/**/*.mdx
📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)
src/content/docs/**/*.mdx: In MDX documentation files,<Steps>must contain one continuous ordered list. Wrap<Steps>around a normal Markdown ordered list such as1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the1. ##,2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images,<Tabs>,<TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside<Steps>. If the content is mostly<Tabs>or other JSX-heavy blocks, use normal section headings instead of<Steps>
In MDX documentation files, when<Tabs>is used inside a step, keep<Tabs>,<TabItem>,</TabItem>, and</Tabs>consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside</Steps>
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
src/content/docs/**/*.{md,mdx}: Every documentation page must include frontmatter with at least:title(≤60 chars),description(≤160 chars), andsidebar.label(1-3 words)
Use H2 for major sections, H3 for subsections, and H4 only inside<Steps>; never use H1 in body content and avoid nesting beyond H4
Use numbered lists only inside<Steps>for ordered procedures; use bulleted lists for unordered information
Use bold for first mention of important terms, UI elements, and dashboard paths; use inline code for technical identifiers (variables, functions, endpoints, scopes, environment variables, file paths, placeholders)
The<Steps>component requires a single continuous ordered list with proper indentation: steps at column 0, continuation content indented with exactly 3 spaces
Use<Aside>component with atitleattribute for cautions, tips, and notes
Use<Badge>component to indicate parameter requirements in tables and inline text
Use<details>blocks at the end of pages for FAQs, common scenarios, and troubleshooting
Split content into clear sections with descriptive, sentence-style titles; include a table of contents for documents with multiple sections; keep paragraphs short and isolate critical points in their own short paragraphs
Begin sections and paragraphs with standalone topic sentences that preview content; put topic words at the beginning to support fast skimming; put key takeaways and results at the top of documents
Use bullets and tables generously to structure information; bold important text to highlight key concepts and decisions
Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns like 'this' or 'that' when the referent is not explicit
Maintain strict consistency in terminology, formatting, and style; do not presume the reader's state of mind or intentions; use direct, instructional language
Write more simply than you think you need to; optimize for readers new to the do...
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/agentkit/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
Agentkit code examples live in the external repo scalekit-developers/agent-auth-examples organized as
javascript/frameworks/<framework>andpython/frameworks/<framework>; verify docs snippets match current implementations in that repo
Files:
src/content/docs/agentkit/connectors/tableau.mdx
🧠 Learnings (39)
📓 Common learnings
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: 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/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: 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.
📚 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-tableau.mdxsrc/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 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-tableau.mdx
📚 Learning: 2026-04-13T10:43:05.628Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 590
File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83
Timestamp: 2026-04-13T10:43:05.628Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T17:03:02.786Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 619
File: src/components/templates/agent-connectors/_usage-posthogmcp.mdx:82-82
Timestamp: 2026-04-20T17:03:02.786Z
Learning: In `src/components/templates/agent-connectors/_usage-posthogmcp.mdx`, the trailing `## Scalekit Tools` heading is intentionally omitted. The parent connector page (`src/content/docs/agentkit/connectors/posthogmcp.mdx`) renders the tool list separately via the `ToolList` component and the imported `tools` dataset, so the structural anchor heading used by other `_usage-*.mdx` templates is not needed here. Do not flag the missing `## Scalekit Tools` heading in this file.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-02-26T07:20:46.903Z
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.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-22T09:58:57.649Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227
Timestamp: 2026-04-22T09:58:57.649Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews.
Applied to files:
src/components/templates/agent-connectors/_setup-tableau.mdxsrc/data/agent-connectors/tableau.tssrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.mdxsrc/content/docs/agentkit/connectors/tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.mdxsrc/components/templates/agent-connectors/_usage-tableau.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-tableau.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-tableau.mdx
📚 Learning: 2026-04-13T10:43:03.024Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 590
File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83
Timestamp: 2026-04-13T10:43:03.024Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, keep the trailing `## Scalekit Tools` heading at the end of each template. Do not flag it as empty or as a duplicate heading in future reviews for these files, since it is an intentional structural anchor used by the parent connector reference page to append the tool-list section beneath the proxy API examples.
Applied to files:
src/components/templates/agent-connectors/_usage-tableau.mdx
📚 Learning: 2026-03-25T15:59:47.933Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 531
File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48
Timestamp: 2026-03-25T15:59:47.933Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, the code snippets are intentionally directional/illustrative and are meant to demonstrate the expected call sequence, not production-ready runnable code. When reviewing these files, do not flag missing `try/except` (Python) or `try/catch` (JS/TS) error handling solely because the snippet omits it—focus on whether the call sequence/pattern is conveyed clearly.
Applied to files:
src/components/templates/agent-connectors/_usage-tableau.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/components/templates/agent-connectors/_usage-tableau.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-tableau.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/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-25T10:15:02.544Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 529
File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190
Timestamp: 2026-03-25T10:15:02.544Z
Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-22T04:05:02.920Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237
Timestamp: 2026-04-22T04:05:02.920Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-01T08:35:26.973Z
Learnt from: srinivaskarre-sk
Repo: scalekit-inc/developer-docs PR: 566
File: src/content/docs/agent-auth/user-verification.mdx:55-117
Timestamp: 2026-04-01T08:35:26.973Z
Learning: In `src/content/docs/agent-auth/user-verification.mdx` and Agent Auth connected accounts documentation (src/content/docs/agent-auth/**/*.mdx), only Python and Node.js SDK support is currently available for Agent Auth features (including connected accounts magic link creation and user verification). Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for these files. Add Go and Java TabItems once those SDKs support Agent Auth/connected account features.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-27T16:55:31.608Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 544
File: src/content/docs/cookbooks/daily-briefing-agent.mdx:0-0
Timestamp: 2026-03-27T16:55:31.608Z
Learning: In `src/content/docs/cookbooks/daily-briefing-agent.mdx`, the `ensureConnected` (TypeScript) and `ensure_connected` (Python) functions intentionally use a single `if` check (not a `while` loop with re-validation) after the OAuth prompt. This is deliberate, well-tested example code reflecting the actual repo pattern. Do not suggest adding retry loops or post-prompt status re-validation in future reviews of this file.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T14:34:06.246Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 618
File: src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx:66-77
Timestamp: 2026-04-20T14:34:06.246Z
Learning: In `src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx`, do not flag the absence of an explicit `state`/CSRF validation warning next to the authorization URL examples in the "Signup/login widgets" section. The page already links to `/authenticate/fsa/implement-login/` where that security guidance is covered. Flagging it here is considered out of scope for this page.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-10T10:37:49.873Z
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:49.873Z
Learning: In `src/components/templates/agent-connectors/`, all connector setup MDX files (e.g., _setup-asana.mdx, _setup-clickup.mdx, _setup-confluence.mdx, _setup-googlecalendar.mdx, _setup-intercom.mdx, _setup-monday.mdx, _setup-notion.mdx, _setup-zoom.mdx) intentionally use a single shared redirect URI screenshot (`use-own-credentials-redirect-uri.png` located under `@/assets/docs/agent-connectors/<connector-name>/`) for all redirect URI-related steps, even when steps show different UIs (e.g., Scalekit dashboard vs. the third-party console). Do not flag reuse of this image across multiple steps within the same connector file as an issue.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-17T16:01:50.487Z
Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
🪛 LanguageTool
src/components/templates/agent-connectors/_usage-tableau.mdx
[style] ~159-~159: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNG”.
Context: .../TabItem> ### Export a view as PNG image <TabItem...
(ACRONYM_TAUTOLOGY)
src/content/docs/agentkit/connectors/tableau.mdx
[style] ~25-~25: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNGs”.
Context: ...sualizations** — Download dashboards as PNG images, PDF documents, or Excel crosstab files...
(ACRONYM_TAUTOLOGY)
🔇 Additional comments (8)
src/data/agent-connectors/tableau.ts (2)
1098-1117: VizQL query params typed asstringbut expect JSON arrays.The
fields,filters, andsortparameters are typed asstringbut their descriptions indicate they should be JSON arrays. This was previously flagged - if theTooltype supportsarray, consider updating these for better schema accuracy.
1-16: LGTM on auth and session tools.The
tableau_auth_signoutandtableau_session_gettools are well-documented with clear descriptions of their purpose and the automatic token refresh behavior.src/content/docs/agentkit/connectors/tableau.mdx (3)
28-28: Documentation claims "update" for users and groups, but no update tools exist.Line 28 states "add, update, and remove users and groups" but
tableau.tsonly defines add/remove operations for users and create/add/remove for groups. Remove "update" to match the actual tool catalog.
55-77: LGTM on resource ID mapping and start sequence.The table mapping resources to their discovery tools is helpful, and the recommended start sequence provides clear guidance for agent implementations. The code block format for the sequence is appropriate for quick reference.
30-39: LGTM on authentication flow documentation.The PAT-based session token flow is clearly explained: store credentials once, Scalekit handles sign-in and refresh automatically with a 5-minute buffer, session token injected as
X-Tableau-Auth. This aligns with the connector implementation.src/components/templates/agent-connectors/_usage-tableau.mdx (2)
1-73: LGTM on site ID retrieval workflow.The examples clearly demonstrate the two-step process: fetching the connected account, then calling
tableau_session_getto retrieve and cache thesite_id. SDK variable naming follows conventions (scalekitfor Node.js,scalekit_clientfor Python).
224-277: LGTM on refresh polling example.The extract refresh workflow correctly demonstrates triggering
tableau_datasource_refresh, extracting the job ID, and pollingtableau_job_getuntil completion. The 10-second polling interval is reasonable for long-running extract jobs.src/components/templates/agent-connectors/_setup-tableau.mdx (1)
7-87: LGTM on setup workflow.The three-step setup process is clear: create PAT in Tableau, create connection in Scalekit, add connected account. The credential fields (
domain,pat_name,pat_secret,site_content_url) align with what the connector needs for automatic session management. SDK variable naming is correct.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
src/content/docs/agentkit/connectors/tableau.mdx (1)
1-13:⚠️ Potential issue | 🟠 MajorAdd missing required frontmatter fields (
description,sidebar.label).These fields are still missing and are required for docs metadata/navigation consistency.
Suggested fix
--- title: Tableau +description: Connect your agent to Tableau to browse content, export views, query data, and manage site resources. +sidebar: + label: Tableau tableOfContents: true connectorIcon: https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/tableau.svg connectorAuthType: API Key connectorCategories: [analytics, business_intelligence, data_visualization] head:As per coding guidelines: Every documentation page must include frontmatter with at least
title,description, andsidebar.label.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/agentkit/connectors/tableau.mdx` around lines 1 - 13, The frontmatter in the Tableau docs (the YAML block at top of src/content/docs/agentkit/connectors/tableau.mdx) is missing required fields; add a descriptive summary and a sidebar label by including `description: "<short one-line summary of the connector>"` and `sidebar.label: "Tableau"` (or another concise label) alongside the existing `title`, `connectorAuthType`, and `connectorCategories` entries so the page meets docs metadata/navigation requirements.
🤖 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/content/docs/agentkit/connectors/tableau.mdx`:
- Around line 72-77: The fenced code block in
src/content/docs/agentkit/connectors/tableau.mdx (the block listing
tableau_session_get, tableau_workbooks_list, tableau_list_views,
tableau_datasources_list) lacks a language identifier; update the opening fence
to include a language (e.g., use ```text) so the MDX renderer treats it
consistently and follows the project's guideline to always specify a fenced-code
language.
---
Duplicate comments:
In `@src/content/docs/agentkit/connectors/tableau.mdx`:
- Around line 1-13: The frontmatter in the Tableau docs (the YAML block at top
of src/content/docs/agentkit/connectors/tableau.mdx) is missing required fields;
add a descriptive summary and a sidebar label by including `description: "<short
one-line summary of the connector>"` and `sidebar.label: "Tableau"` (or another
concise label) alongside the existing `title`, `connectorAuthType`, and
`connectorCategories` entries so the page meets docs metadata/navigation
requirements.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: a0920b79-5e81-4d9d-82ca-09eb3322fef5
📒 Files selected for processing (2)
src/content/docs/agentkit/connectors/tableau.mdxsrc/data/agent-connectors/tableau.ts
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Redirect rules - scalekit-starlight
- GitHub Check: Header rules - scalekit-starlight
- GitHub Check: Pages changed - scalekit-starlight
🧰 Additional context used
📓 Path-based instructions (11)
**/*.{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/data/agent-connectors/tableau.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/data/agent-connectors/tableau.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/data/agent-connectors/tableau.ts
**/*.{js,ts,tsx,py,go,java}
📄 CodeRabbit inference engine (AGENTS.md)
Use exact SDK variable names: Node.js:
scalekit, Python:scalekit_client, Go:scalekitClient, Java:scalekitClient
Files:
src/data/agent-connectors/tableau.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/data/agent-connectors/tableau.ts
**/*.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. ## Titlewith 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/agentkit/connectors/tableau.mdx
⚙️ CodeRabbit configuration file
**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:Frontmatter
titleMUST be ≤ 60 characters and clearly state what the page does.descriptionMUST be ≤ 160 characters, action-oriented, unique per page.sidebar.labelMUST be present and ≤ 30 characters.sidebar.orderMUST 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/nextlinks 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
- Journey how-to guides MUST contain numbered
<Steps>(Starlight
component). This does NOT apply tosrc/content/docs/cookbooks/**
(blog-style recipes — optional<Steps>,<Tabs>after</Steps>OK;
see cookbookspath_instructions).- 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...
Files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
src/content/docs/**/*.mdx
📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)
src/content/docs/**/*.mdx: In MDX documentation files,<Steps>must contain one continuous ordered list. Wrap<Steps>around a normal Markdown ordered list such as1. ## ...
In MDX documentation files, numbered step lines must start at column 0. Do not indent the1. ##,2. ##, etc.
In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images,<Tabs>,<TabItem>, and fenced code blocks
In MDX documentation files, prefer plain Markdown inside<Steps>. If the content is mostly<Tabs>or other JSX-heavy blocks, use normal section headings instead of<Steps>
In MDX documentation files, when<Tabs>is used inside a step, keep<Tabs>,<TabItem>,</TabItem>, and</Tabs>consistently nested under that step
In MDX documentation files, if a tabs block is not part of a numbered step, place it outside</Steps>
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
src/content/docs/**/*.{md,mdx}: Every documentation page must include frontmatter with at least:title(≤60 chars),description(≤160 chars), andsidebar.label(1-3 words)
Use H2 for major sections, H3 for subsections, and H4 only inside<Steps>; never use H1 in body content and avoid nesting beyond H4
Use numbered lists only inside<Steps>for ordered procedures; use bulleted lists for unordered information
Use bold for first mention of important terms, UI elements, and dashboard paths; use inline code for technical identifiers (variables, functions, endpoints, scopes, environment variables, file paths, placeholders)
The<Steps>component requires a single continuous ordered list with proper indentation: steps at column 0, continuation content indented with exactly 3 spaces
Use<Aside>component with atitleattribute for cautions, tips, and notes
Use<Badge>component to indicate parameter requirements in tables and inline text
Use<details>blocks at the end of pages for FAQs, common scenarios, and troubleshooting
Split content into clear sections with descriptive, sentence-style titles; include a table of contents for documents with multiple sections; keep paragraphs short and isolate critical points in their own short paragraphs
Begin sections and paragraphs with standalone topic sentences that preview content; put topic words at the beginning to support fast skimming; put key takeaways and results at the top of documents
Use bullets and tables generously to structure information; bold important text to highlight key concepts and decisions
Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns like 'this' or 'that' when the referent is not explicit
Maintain strict consistency in terminology, formatting, and style; do not presume the reader's state of mind or intentions; use direct, instructional language
Write more simply than you think you need to; optimize for readers new to the do...
Files:
src/content/docs/agentkit/connectors/tableau.mdx
src/content/docs/agentkit/**/*.{md,mdx}
📄 CodeRabbit inference engine (CLAUDE.md)
Agentkit code examples live in the external repo scalekit-developers/agent-auth-examples organized as
javascript/frameworks/<framework>andpython/frameworks/<framework>; verify docs snippets match current implementations in that repo
Files:
src/content/docs/agentkit/connectors/tableau.mdx
🧠 Learnings (33)
📓 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: 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: 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: 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: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237
Timestamp: 2026-04-22T04:05:02.920Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature.
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.
📚 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/data/agent-connectors/tableau.tssrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-22T09:58:57.649Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227
Timestamp: 2026-04-22T09:58:57.649Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews.
Applied to files:
src/data/agent-connectors/tableau.tssrc/content/docs/agentkit/connectors/tableau.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/data/agent-connectors/tableau.tssrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T11:30:52.410Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-20T11:30:52.410Z
Learning: Applies to **/*.{md,mdx} : Use consistent terminology throughout; prefer standard names over synonyms
Applied to files:
src/data/agent-connectors/tableau.ts
📚 Learning: 2026-04-13T10:43:05.628Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 590
File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83
Timestamp: 2026-04-13T10:43:05.628Z
Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files.
Applied to files:
src/data/agent-connectors/tableau.tssrc/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T17:03:02.786Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 619
File: src/components/templates/agent-connectors/_usage-posthogmcp.mdx:82-82
Timestamp: 2026-04-20T17:03:02.786Z
Learning: In `src/components/templates/agent-connectors/_usage-posthogmcp.mdx`, the trailing `## Scalekit Tools` heading is intentionally omitted. The parent connector page (`src/content/docs/agentkit/connectors/posthogmcp.mdx`) renders the tool list separately via the `ToolList` component and the imported `tools` dataset, so the structural anchor heading used by other `_usage-*.mdx` templates is not needed here. Do not flag the missing `## Scalekit Tools` heading in this file.
Applied to files:
src/data/agent-connectors/tableau.tssrc/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-02-26T07:20:46.903Z
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.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-12T05:02:13.454Z
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.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-25T10:15:02.544Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 529
File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190
Timestamp: 2026-03-25T10:15:02.544Z
Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-01T08:35:26.973Z
Learnt from: srinivaskarre-sk
Repo: scalekit-inc/developer-docs PR: 566
File: src/content/docs/agent-auth/user-verification.mdx:55-117
Timestamp: 2026-04-01T08:35:26.973Z
Learning: In `src/content/docs/agent-auth/user-verification.mdx` and Agent Auth connected accounts documentation (src/content/docs/agent-auth/**/*.mdx), only Python and Node.js SDK support is currently available for Agent Auth features (including connected accounts magic link creation and user verification). Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for these files. Add Go and Java TabItems once those SDKs support Agent Auth/connected account features.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-22T04:05:02.920Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 623
File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237
Timestamp: 2026-04-22T04:05:02.920Z
Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-27T16:55:31.608Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 544
File: src/content/docs/cookbooks/daily-briefing-agent.mdx:0-0
Timestamp: 2026-03-27T16:55:31.608Z
Learning: In `src/content/docs/cookbooks/daily-briefing-agent.mdx`, the `ensureConnected` (TypeScript) and `ensure_connected` (Python) functions intentionally use a single `if` check (not a `while` loop with re-validation) after the OAuth prompt. This is deliberate, well-tested example code reflecting the actual repo pattern. Do not suggest adding retry loops or post-prompt status re-validation in future reviews of this file.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T14:34:06.246Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 618
File: src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx:66-77
Timestamp: 2026-04-20T14:34:06.246Z
Learning: In `src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx`, do not flag the absence of an explicit `state`/CSRF validation warning next to the authorization URL examples in the "Signup/login widgets" section. The page already links to `/authenticate/fsa/implement-login/` where that security guidance is covered. Flagging it here is considered out of scope for this page.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-10T10:37:49.873Z
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:49.873Z
Learning: In `src/components/templates/agent-connectors/`, all connector setup MDX files (e.g., _setup-asana.mdx, _setup-clickup.mdx, _setup-confluence.mdx, _setup-googlecalendar.mdx, _setup-intercom.mdx, _setup-monday.mdx, _setup-notion.mdx, _setup-zoom.mdx) intentionally use a single shared redirect URI screenshot (`use-own-credentials-redirect-uri.png` located under `@/assets/docs/agent-connectors/<connector-name>/`) for all redirect URI-related steps, even when steps show different UIs (e.g., Scalekit dashboard vs. the third-party console). Do not flag reuse of this image across multiple steps within the same connector file as an issue.
Applied to files:
src/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-20T11:29:40.242Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-04-20T11:29:40.242Z
Learning: Applies to src/content/docs/**/*.{md,mdx} : Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words)
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/content/docs/agentkit/connectors/tableau.mdx
📚 Learning: 2026-04-13T14:22:37.194Z
Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 591
File: src/content/docs/reference/agent-connectors/calendly.mdx:47-47
Timestamp: 2026-04-13T14:22:37.194Z
Learning: In `src/content/docs/reference/agent-connectors/` MDX files (agent-connector reference pages, e.g., calendly.mdx), the `title` attribute on `<Aside>` components is not required. Do not flag missing `title` props on `<Aside>` components in files under this directory. This is a deliberate exception to the global rule requiring `title` on all `<Aside>` components.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
📚 Learning: 2026-03-17T16:01:50.487Z
Learnt from: dhaneshbs
Repo: scalekit-inc/developer-docs PR: 506
File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853
Timestamp: 2026-03-17T16:01:50.487Z
Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users.
Applied to files:
src/content/docs/agentkit/connectors/tableau.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/agentkit/connectors/tableau.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/agentkit/connectors/tableau.mdx
🪛 LanguageTool
src/content/docs/agentkit/connectors/tableau.mdx
[style] ~25-~25: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNGs”.
Context: ...sualizations** — Download dashboards as PNG images, PDF documents, or Excel crosstab files...
(ACRONYM_TAUTOLOGY)
🔇 Additional comments (1)
src/data/agent-connectors/tableau.ts (1)
1098-1117: Good improvement: VizQL payload params are now correctly modeled as arrays.
fields,filters, andsortnow match the documented structured payload shape, which improves tool contract clarity.
…or tools, add workbook_search
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
src/content/docs/agentkit/connectors/tableau.mdx (3)
1-7:⚠️ Potential issue | 🟠 MajorAdd required frontmatter metadata (
description,sidebar.label).Line 1-7 is missing required frontmatter fields used for docs navigation and discovery.
Suggested fix
--- title: Tableau +description: Connect your agent to list, export, and manage Tableau resources with Scalekit tools and proxy calls. +sidebar: + label: Tableau tableOfContents: true connectorIcon: https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/tableau.svg connectorAuthType: API Key connectorCategories: [analytics, business_intelligence, data_visualization]As per coding guidelines: “Every documentation page must include frontmatter with at least:
title,description, andsidebar.label.”🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/agentkit/connectors/tableau.mdx` around lines 1 - 7, The frontmatter for the Tableau docs is missing required fields; update the top YAML block (where title, tableOfContents, connectorIcon, connectorAuthType, connectorCategories, head are defined) to include description and sidebar.label keys—add a brief descriptive sentence for description and a concise label for sidebar.label so the page meets docs navigation and discovery requirements.
73-77:⚠️ Potential issue | 🟡 MinorAdd a language identifier to the fenced sequence block.
Line 73 starts a bare fenced code block; add an explicit language for consistent MDX rendering.
Suggested fix
-``` +```text 1. tableau_workbooks_list → discover workbooks 2. tableau_list_views → discover views within a workbook 3. tableau_datasources_list → discover data sources</details> As per coding guidelines: “Use fenced code blocks with language identifiers for all code.” <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@src/content/docs/agentkit/connectors/tableau.mdxaround lines 73 - 77, The
fenced list block showing tableau_workbooks_list / tableau_list_views /
tableau_datasources_list is missing a language identifier; update that fenced
code block (the triple-backtick block containing those three lines) to include a
language tag such as "text" (i.e., changetotext) so MDX renders
consistently and follows the guideline to use fenced code blocks with language
identifiers.</details> --- `28-28`: _⚠️ Potential issue_ | _🟠 Major_ **Remove unsupported “update site settings” claim from capabilities.** Line 28 advertises “update site settings,” but `src/data/agent-connectors/tableau.ts` does not expose a corresponding update tool. This creates a docs-to-tooling contract mismatch. <details> <summary>Suggested fix</summary> ```diff -- **Manage the site** — Create and update projects; add and remove users; create, add, and remove groups; update site settings +- **Manage the site** — Retrieve site details, create and update projects, add and remove users, and manage groups ``` </details> <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@src/content/docs/agentkit/connectors/tableau.mdx` at line 28, The docs list the capability "Manage the site" and specifically mention "update site settings", but there is no corresponding update tool exposed by the Tableau connector, so remove the unsupported phrase "update site settings" from the "Manage the site" bullet in the docs (or alternatively implement an updateSiteSettings tool in the Tableau connector if that capability is intended); ensure the documentation text and the connector's exposed toolset remain consistent by only advertising actions implemented by the connector. ``` </details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In@src/content/docs/agentkit/connectors/tableau.mdx:
- Around line 1-7: The frontmatter for the Tableau docs is missing required
fields; update the top YAML block (where title, tableOfContents, connectorIcon,
connectorAuthType, connectorCategories, head are defined) to include description
and sidebar.label keys—add a brief descriptive sentence for description and a
concise label for sidebar.label so the page meets docs navigation and discovery
requirements.- Around line 73-77: The fenced list block showing tableau_workbooks_list /
tableau_list_views / tableau_datasources_list is missing a language identifier;
update that fenced code block (the triple-backtick block containing those three
lines) to include a language tag such as "text" (i.e., changetotext) so
MDX renders consistently and follows the guideline to use fenced code blocks
with language identifiers.- Line 28: The docs list the capability "Manage the site" and specifically
mention "update site settings", but there is no corresponding update tool
exposed by the Tableau connector, so remove the unsupported phrase "update site
settings" from the "Manage the site" bullet in the docs (or alternatively
implement an updateSiteSettings tool in the Tableau connector if that capability
is intended); ensure the documentation text and the connector's exposed toolset
remain consistent by only advertising actions implemented by the connector.</details> --- <details> <summary>ℹ️ Review info</summary> <details> <summary>⚙️ Run configuration</summary> **Configuration used**: Path: .coderabbit.yaml **Review profile**: ASSERTIVE **Plan**: Pro **Run ID**: `e7d8efde-806f-4962-b5f6-abc3ccf9e441` </details> <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between cee2e099944fbf8a2136437e60753e4c1b06df64 and 32bb7995f3f70fb2800b64b6df19340a288217b1. </details> <details> <summary>📒 Files selected for processing (3)</summary> * `src/components/templates/agent-connectors/_usage-tableau.mdx` * `src/content/docs/agentkit/connectors/tableau.mdx` * `src/data/agent-connectors/tableau.ts` </details> </details> <details> <summary>📜 Review details</summary> <details> <summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)</summary> * GitHub Check: Redirect rules - scalekit-starlight * GitHub Check: Header rules - scalekit-starlight * GitHub Check: Pages changed - scalekit-starlight </details> <details> <summary>🧰 Additional context used</summary> <details> <summary>📓 Path-based instructions (11)</summary> <details> <summary>**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy,gradle,xml,json}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,jsx}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,py,go,java}</summary> **📄 CodeRabbit inference engine (AGENTS.md)** > Use exact SDK variable names: Node.js: `scalekit`, Python: `scalekit_client`, Go: `scalekitClient`, Java: `scalekitClient` Files: - `src/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{ts,js,mjs}</summary> **⚙️ 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.mdx</summary> **📄 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.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 > - Journey how-to guides MUST contain numbered `<Steps>` (Starlight > component). This does NOT apply to `src/content/docs/cookbooks/**` > (blog-style recipes — optional `<Steps>`, `<Tabs>` after `</Steps>` OK; > see cookbooks `path_instructions`). > - 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... Files: - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>**/*.{yml,yaml,md,mdx}</summary> **📄 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>**/*.{md,mdx}</summary> **📄 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>src/content/docs/**/*.mdx</summary> **📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)** > `src/content/docs/**/*.mdx`: In MDX documentation files, `<Steps>` must contain one continuous ordered list. Wrap `<Steps>` around a normal Markdown ordered list such as `1. ## ...` > In MDX documentation files, numbered step lines must start at column 0. Do not indent the `1. ##`, `2. ##`, etc. > In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images, `<Tabs>`, `<TabItem>`, and fenced code blocks > In MDX documentation files, prefer plain Markdown inside `<Steps>`. If the content is mostly `<Tabs>` or other JSX-heavy blocks, use normal section headings instead of `<Steps>` > In MDX documentation files, when `<Tabs>` is used inside a step, keep `<Tabs>`, `<TabItem>`, `</TabItem>`, and `</Tabs>` consistently nested under that step > In MDX documentation files, if a tabs block is not part of a numbered step, place it outside `</Steps>` Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>src/content/docs/**/*.{md,mdx}</summary> **📄 CodeRabbit inference engine (CLAUDE.md)** > `src/content/docs/**/*.{md,mdx}`: Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words) > Use H2 for major sections, H3 for subsections, and H4 only inside `<Steps>`; never use H1 in body content and avoid nesting beyond H4 > Use numbered lists only inside `<Steps>` for ordered procedures; use bulleted lists for unordered information > Use bold for first mention of important terms, UI elements, and dashboard paths; use inline code for technical identifiers (variables, functions, endpoints, scopes, environment variables, file paths, placeholders) > The `<Steps>` component requires a single continuous ordered list with proper indentation: steps at column 0, continuation content indented with exactly 3 spaces > Use `<Aside>` component with a `title` attribute for cautions, tips, and notes > Use `<Badge>` component to indicate parameter requirements in tables and inline text > Use `<details>` blocks at the end of pages for FAQs, common scenarios, and troubleshooting > Split content into clear sections with descriptive, sentence-style titles; include a table of contents for documents with multiple sections; keep paragraphs short and isolate critical points in their own short paragraphs > Begin sections and paragraphs with standalone topic sentences that preview content; put topic words at the beginning to support fast skimming; put key takeaways and results at the top of documents > Use bullets and tables generously to structure information; bold important text to highlight key concepts and decisions > Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns like 'this' or 'that' when the referent is not explicit > Maintain strict consistency in terminology, formatting, and style; do not presume the reader's state of mind or intentions; use direct, instructional language > Write more simply than you think you need to; optimize for readers new to the do... Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>src/content/docs/agentkit/**/*.{md,mdx}</summary> **📄 CodeRabbit inference engine (CLAUDE.md)** > Agentkit code examples live in the external repo **scalekit-developers/agent-auth-examples** organized as `javascript/frameworks/<framework>` and `python/frameworks/<framework>`; verify docs snippets match current implementations in that repo Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> </details><details> <summary>🧠 Learnings (47)</summary> <details> <summary>📓 Common learnings</summary> ``` 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: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 590 File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83 Timestamp: 2026-04-13T10:43:05.628Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files. ``` ``` 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: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227 Timestamp: 2026-04-22T09:58:57.649Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews. ``` ``` 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: 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: 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: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237 Timestamp: 2026-04-22T04:05:02.920Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature. ``` ``` 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: 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: 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 ``` ``` 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. ``` </details> <details> <summary>📚 Learning: 2026-02-26T07:22:55.583Z</summary> ``` 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/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:21:37.207Z</summary> ``` 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/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-22T09:58:57.649Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227 Timestamp: 2026-04-22T09:58:57.649Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Use consistent terminology throughout; prefer standard names over synonyms ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` </details> <details> <summary>📚 Learning: 2026-04-13T10:43:05.628Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 590 File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83 Timestamp: 2026-04-13T10:43:05.628Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T17:03:02.786Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 619 File: src/components/templates/agent-connectors/_usage-posthogmcp.mdx:82-82 Timestamp: 2026-04-20T17:03:02.786Z Learning: In `src/components/templates/agent-connectors/_usage-posthogmcp.mdx`, the trailing `## Scalekit Tools` heading is intentionally omitted. The parent connector page (`src/content/docs/agentkit/connectors/posthogmcp.mdx`) renders the tool list separately via the `ToolList` component and the imported `tools` dataset, so the structural anchor heading used by other `_usage-*.mdx` templates is not needed here. Do not flag the missing `## Scalekit Tools` heading in this file. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:23:27.672Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-13T03:44:23.786Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:20:46.903Z</summary> ``` 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. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T05:02:13.454Z</summary> ``` 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. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T05:02:13.454Z</summary> ``` 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. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:28:42.817Z</summary> ``` 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:18:51.377Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-25T10:15:02.544Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 529 File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190 Timestamp: 2026-03-25T10:15:02.544Z Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-01T08:35:26.973Z</summary> ``` Learnt from: srinivaskarre-sk Repo: scalekit-inc/developer-docs PR: 566 File: src/content/docs/agent-auth/user-verification.mdx:55-117 Timestamp: 2026-04-01T08:35:26.973Z Learning: In `src/content/docs/agent-auth/user-verification.mdx` and Agent Auth connected accounts documentation (src/content/docs/agent-auth/**/*.mdx), only Python and Node.js SDK support is currently available for Agent Auth features (including connected accounts magic link creation and user verification). Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for these files. Add Go and Java TabItems once those SDKs support Agent Auth/connected account features. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-22T04:05:02.920Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237 Timestamp: 2026-04-22T04:05:02.920Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:29:16.422Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-27T16:55:31.608Z</summary> ``` Learnt from: saif-at-scalekit Repo: scalekit-inc/developer-docs PR: 544 File: src/content/docs/cookbooks/daily-briefing-agent.mdx:0-0 Timestamp: 2026-03-27T16:55:31.608Z Learning: In `src/content/docs/cookbooks/daily-briefing-agent.mdx`, the `ensureConnected` (TypeScript) and `ensure_connected` (Python) functions intentionally use a single `if` check (not a `while` loop with re-validation) after the OAuth prompt. This is deliberate, well-tested example code reflecting the actual repo pattern. Do not suggest adding retry loops or post-prompt status re-validation in future reviews of this file. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T14:34:06.246Z</summary> ``` Learnt from: saif-at-scalekit Repo: scalekit-inc/developer-docs PR: 618 File: src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx:66-77 Timestamp: 2026-04-20T14:34:06.246Z Learning: In `src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx`, do not flag the absence of an explicit `state`/CSRF validation warning next to the authorization URL examples in the "Signup/login widgets" section. The page already links to `/authenticate/fsa/implement-login/` where that security guidance is covered. Flagging it here is considered out of scope for this page. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:37:49.873Z</summary> ``` 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:49.873Z Learning: In `src/components/templates/agent-connectors/`, all connector setup MDX files (e.g., _setup-asana.mdx, _setup-clickup.mdx, _setup-confluence.mdx, _setup-googlecalendar.mdx, _setup-intercom.mdx, _setup-monday.mdx, _setup-notion.mdx, _setup-zoom.mdx) intentionally use a single shared redirect URI screenshot (`use-own-credentials-redirect-uri.png` located under `@/assets/docs/agent-connectors/<connector-name>/`) for all redirect URI-related steps, even when steps show different UIs (e.g., Scalekit dashboard vs. the third-party console). Do not flag reuse of this image across multiple steps within the same connector file as an issue. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:29:40.242Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: CLAUDE.md:0-0 Timestamp: 2026-04-20T11:29:40.242Z Learning: Applies to src/content/docs/**/*.{md,mdx} : Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words) ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-13T14:22:37.194Z</summary> ``` Learnt from: Pranesh-Raghu Repo: scalekit-inc/developer-docs PR: 591 File: src/content/docs/reference/agent-connectors/calendly.mdx:47-47 Timestamp: 2026-04-13T14:22:37.194Z Learning: In `src/content/docs/reference/agent-connectors/` MDX files (agent-connector reference pages, e.g., calendly.mdx), the `title` attribute on `<Aside>` components is not required. Do not flag missing `title` props on `<Aside>` components in files under this directory. This is a deliberate exception to the global rule requiring `title` on all `<Aside>` components. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-16T21:02:51.181Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: .cursor/rules/expressive-code.mdc:0-0 Timestamp: 2026-03-16T21:02:51.181Z Learning: Applies to **/*.{md,mdx} : Always add a language identifier to fenced code blocks (e.g., `js` not just bare backticks) ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:29:40.242Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: CLAUDE.md:0-0 Timestamp: 2026-04-20T11:29:40.242Z Learning: Applies to src/content/docs/**/*.{md,mdx} : Use fenced code blocks with language identifiers for all code; never use screenshots of code ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-16T21:02:51.181Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: .cursor/rules/expressive-code.mdc:0-0 Timestamp: 2026-03-16T21:02:51.181Z Learning: Applies to **/*.{md,mdx} : Ensure every code example has a language identifier set via `lang` prop or fenced language id ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Prefer fenced code blocks with language identifiers for all code; never use screenshots of code ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Use language tabs with clear framework titles for code examples ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 appropriate syntax highlighting language from 200+ supported languages in code blocks ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 consistent Tab labels for multi-language examples: 'Node.js', 'Python', 'Go', 'Java' with TabItem values 'node', 'python'/'py', 'go'/'golang', 'java' ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 'title' attribute in code blocks to show framework names: 'Express.js', 'Flask', 'Gin', 'Spring Boot' ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-30T18:18:50.883Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-04T12:47:16.544Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T08:57:12.201Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T13:04:27.491Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-05T11:29:08.125Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T07:27:56.794Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T07:32:38.426Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-17T16:01:50.487Z</summary> ``` Learnt from: dhaneshbs Repo: scalekit-inc/developer-docs PR: 506 File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853 Timestamp: 2026-03-17T16:01:50.487Z Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T03:34:41.147Z</summary>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 thecomponent. 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T18:41:00.639Z</summary> ``` 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/agentkit/connectors/tableau.mdx` - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-13T10:43:03.024Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 590 File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83 Timestamp: 2026-04-13T10:43:03.024Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, keep the trailing `## Scalekit Tools` heading at the end of each template. Do not flag it as empty or as a duplicate heading in future reviews for these files, since it is an intentional structural anchor used by the parent connector reference page to append the tool-list section beneath the proxy API examples. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-25T15:59:47.933Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 531 File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48 Timestamp: 2026-03-25T15:59:47.933Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, the code snippets are intentionally directional/illustrative and are meant to demonstrate the expected call sequence, not production-ready runnable code. When reviewing these files, do not flag missing `try/except` (Python) or `try/catch` (JS/TS) error handling solely because the snippet omits it—focus on whether the call sequence/pattern is conveyed clearly. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T15:06:49.617Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:37:47.033Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:38:27.783Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:26:39.422Z</summary> ``` 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-tableau.mdx` </details> </details><details> <summary>🪛 LanguageTool</summary> <details> <summary>src/content/docs/agentkit/connectors/tableau.mdx</summary> [style] ~25-~25: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNGs”. Context: ...sualizations** — Download dashboards as PNG images, PDF documents, or Excel crosstab files... (ACRONYM_TAUTOLOGY) </details> </details> </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (2)
src/content/docs/agentkit/connectors/tableau.mdx (2)
73-77:⚠️ Potential issue | 🟡 MinorAdd a language identifier to the fenced block.
Use an explicit language (for example,
text) for consistent MDX rendering and linting.Proposed fix
-``` +```text 1. tableau_workbooks_list → discover workbooks 2. tableau_list_views → discover views within a workbook 3. tableau_datasources_list → discover data sources</details> As per coding guidelines: "Always add a language identifier to fenced code blocks (e.g., `js` not just bare backticks)". <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@src/content/docs/agentkit/connectors/tableau.mdxaround lines 73 - 77, The
fenced code block that lists tableau connector commands (containing
"tableau_workbooks_list", "tableau_list_views", and "tableau_datasources_list")
is missing a language identifier; update the opening backticks to include a
language (e.g., use ```text) so the block becomes a labeled fenced code block
for consistent MDX rendering and linting.</details> --- `1-13`: _⚠️ Potential issue_ | _🟠 Major_ **Add required frontmatter fields (`description`, `sidebar.label`).** Both fields are required for docs pages under `src/content/docs/**` and are currently missing. <details> <summary>Proposed fix</summary> ```diff --- title: Tableau +description: Connect your agent to browse Tableau resources, export views, and manage site entities using Scalekit tools. +sidebar: + label: Tableau tableOfContents: true connectorIcon: https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/tableau.svg connectorAuthType: API Key connectorCategories: [analytics, business_intelligence, data_visualization] head: ``` </details> As per coding guidelines: "Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words)". <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@src/content/docs/agentkit/connectors/tableau.mdx` around lines 1 - 13, The frontmatter for the Tableau docs page is missing required fields; update the MDX frontmatter block (where title: Tableau is defined) to add a concise description (<=160 chars) and a sidebar.label (1-3 words) alongside the existing title, tableOfContents, connectorIcon, connectorAuthType, and connectorCategories fields; ensure title remains <=60 chars and the new description and sidebar.label meet the length/word constraints per the docs guidelines. ``` </details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In@src/content/docs/agentkit/connectors/tableau.mdx:
- Around line 73-77: The fenced code block that lists tableau connector commands
(containing "tableau_workbooks_list", "tableau_list_views", and
"tableau_datasources_list") is missing a language identifier; update the opening
backticks to include a language (e.g., use ```text) so the block becomes a
labeled fenced code block for consistent MDX rendering and linting.- Around line 1-13: The frontmatter for the Tableau docs page is missing
required fields; update the MDX frontmatter block (where title: Tableau is
defined) to add a concise description (<=160 chars) and a sidebar.label (1-3
words) alongside the existing title, tableOfContents, connectorIcon,
connectorAuthType, and connectorCategories fields; ensure title remains <=60
chars and the new description and sidebar.label meet the length/word constraints
per the docs guidelines.</details> --- <details> <summary>ℹ️ Review info</summary> <details> <summary>⚙️ Run configuration</summary> **Configuration used**: Path: .coderabbit.yaml **Review profile**: ASSERTIVE **Plan**: Pro **Run ID**: `d6e7b4f0-1a13-4bb1-82fb-80ba7c43be19` </details> <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 32bb7995f3f70fb2800b64b6df19340a288217b1 and f4e8e5475b6058a5f6d612ddeb057f7020469cbc. </details> <details> <summary>📒 Files selected for processing (3)</summary> * `src/components/templates/agent-connectors/_usage-tableau.mdx` * `src/content/docs/agentkit/connectors/tableau.mdx` * `src/data/agent-connectors/tableau.ts` </details> </details> <details> <summary>📜 Review details</summary> <details> <summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)</summary> * GitHub Check: Redirect rules - scalekit-starlight * GitHub Check: Header rules - scalekit-starlight * GitHub Check: Pages changed - scalekit-starlight </details> <details> <summary>🧰 Additional context used</summary> <details> <summary>📓 Path-based instructions (11)</summary> <details> <summary>**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy,gradle,xml,json}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,jsx,py,java,cs,go,cpp,c,rb,php,swift,kt,scala,rs,m,mm,groovy}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,jsx}</summary> **📄 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{js,ts,tsx,py,go,java}</summary> **📄 CodeRabbit inference engine (AGENTS.md)** > Use exact SDK variable names: Node.js: `scalekit`, Python: `scalekit_client`, Go: `scalekitClient`, Java: `scalekitClient` Files: - `src/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.{ts,js,mjs}</summary> **⚙️ 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/data/agent-connectors/tableau.ts` </details> <details> <summary>**/*.mdx</summary> **📄 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/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.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 > - Journey how-to guides MUST contain numbered `<Steps>` (Starlight > component). This does NOT apply to `src/content/docs/cookbooks/**` > (blog-style recipes — optional `<Steps>`, `<Tabs>` after `</Steps>` OK; > see cookbooks `path_instructions`). > - 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... Files: - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>**/*.{yml,yaml,md,mdx}</summary> **📄 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/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>**/*.{md,mdx}</summary> **📄 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/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>src/content/docs/**/*.mdx</summary> **📄 CodeRabbit inference engine (.cursor/rules/starlight-steps-tabs-structure.mdc)** > `src/content/docs/**/*.mdx`: In MDX documentation files, `<Steps>` must contain one continuous ordered list. Wrap `<Steps>` around a normal Markdown ordered list such as `1. ## ...` > In MDX documentation files, numbered step lines must start at column 0. Do not indent the `1. ##`, `2. ##`, etc. > In MDX documentation files, any content that belongs to a step must be indented with 3 spaces: paragraphs, bullets, images, `<Tabs>`, `<TabItem>`, and fenced code blocks > In MDX documentation files, prefer plain Markdown inside `<Steps>`. If the content is mostly `<Tabs>` or other JSX-heavy blocks, use normal section headings instead of `<Steps>` > In MDX documentation files, when `<Tabs>` is used inside a step, keep `<Tabs>`, `<TabItem>`, `</TabItem>`, and `</Tabs>` consistently nested under that step > In MDX documentation files, if a tabs block is not part of a numbered step, place it outside `</Steps>` Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>src/content/docs/**/*.{md,mdx}</summary> **📄 CodeRabbit inference engine (CLAUDE.md)** > `src/content/docs/**/*.{md,mdx}`: Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words) > Use H2 for major sections, H3 for subsections, and H4 only inside `<Steps>`; never use H1 in body content and avoid nesting beyond H4 > Use numbered lists only inside `<Steps>` for ordered procedures; use bulleted lists for unordered information > Use bold for first mention of important terms, UI elements, and dashboard paths; use inline code for technical identifiers (variables, functions, endpoints, scopes, environment variables, file paths, placeholders) > The `<Steps>` component requires a single continuous ordered list with proper indentation: steps at column 0, continuation content indented with exactly 3 spaces > Use `<Aside>` component with a `title` attribute for cautions, tips, and notes > Use `<Badge>` component to indicate parameter requirements in tables and inline text > Use `<details>` blocks at the end of pages for FAQs, common scenarios, and troubleshooting > Split content into clear sections with descriptive, sentence-style titles; include a table of contents for documents with multiple sections; keep paragraphs short and isolate critical points in their own short paragraphs > Begin sections and paragraphs with standalone topic sentences that preview content; put topic words at the beginning to support fast skimming; put key takeaways and results at the top of documents > Use bullets and tables generously to structure information; bold important text to highlight key concepts and decisions > Keep sentences simple, right-branching, and unambiguous; avoid ambiguous noun stacks and demonstrative pronouns like 'this' or 'that' when the referent is not explicit > Maintain strict consistency in terminology, formatting, and style; do not presume the reader's state of mind or intentions; use direct, instructional language > Write more simply than you think you need to; optimize for readers new to the do... Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>src/content/docs/agentkit/**/*.{md,mdx}</summary> **📄 CodeRabbit inference engine (CLAUDE.md)** > Agentkit code examples live in the external repo **scalekit-developers/agent-auth-examples** organized as `javascript/frameworks/<framework>` and `python/frameworks/<framework>`; verify docs snippets match current implementations in that repo Files: - `src/content/docs/agentkit/connectors/tableau.mdx` </details> </details><details> <summary>🧠 Learnings (47)</summary> <details> <summary>📓 Common learnings</summary> ``` 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: 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: 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: 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: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237 Timestamp: 2026-04-22T04:05:02.920Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature. ``` ``` 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: 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: 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 ``` ``` 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: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227 Timestamp: 2026-04-22T09:59:00.346Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews. ``` </details> <details> <summary>📚 Learning: 2026-02-26T07:22:55.583Z</summary> ``` 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/data/agent-connectors/tableau.ts` - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-22T09:59:00.346Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:197-227 Timestamp: 2026-04-22T09:59:00.346Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the `execute_tool` code examples (Node.js and Python) under the "MCP tool calling" section intentionally omit client initialization boilerplate (`ScalekitClient` setup, env loading, variable declarations). They are continuation snippets that rely on the client already defined in the `list_scoped_tools` discovery block above. Do not flag these as lacking self-contained initialization in future reviews. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:21:37.207Z</summary> ``` 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/data/agent-connectors/tableau.ts` - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-13T10:43:05.628Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 590 File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83 Timestamp: 2026-04-13T10:43:05.628Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` files, the trailing `## Scalekit Tools` heading at the end of every usage template is intentional and consistent across all 42+ connector usage templates. It acts as a structural anchor/separator that the parent connector reference page uses to append the tool-list section beneath the proxy API examples. Do not flag this heading as empty or duplicate in future reviews of these template files. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Use consistent terminology throughout; prefer standard names over synonyms ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` </details> <details> <summary>📚 Learning: 2026-04-20T17:03:02.786Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 619 File: src/components/templates/agent-connectors/_usage-posthogmcp.mdx:82-82 Timestamp: 2026-04-20T17:03:02.786Z Learning: In `src/components/templates/agent-connectors/_usage-posthogmcp.mdx`, the trailing `## Scalekit Tools` heading is intentionally omitted. The parent connector page (`src/content/docs/agentkit/connectors/posthogmcp.mdx`) renders the tool list separately via the `ToolList` component and the imported `tools` dataset, so the structural anchor heading used by other `_usage-*.mdx` templates is not needed here. Do not flag the missing `## Scalekit Tools` heading in this file. ``` **Applied to files:** - `src/data/agent-connectors/tableau.ts` - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-13T10:43:03.024Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 590 File: src/components/templates/agent-connectors/_usage-databricks.mdx:83-83 Timestamp: 2026-04-13T10:43:03.024Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, keep the trailing `## Scalekit Tools` heading at the end of each template. Do not flag it as empty or as a duplicate heading in future reviews for these files, since it is an intentional structural anchor used by the parent connector reference page to append the tool-list section beneath the proxy API examples. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T05:02:13.454Z</summary> ``` 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. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T05:02:13.454Z</summary> ``` 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. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:23:27.672Z</summary> ``` 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-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:28:42.817Z</summary> ``` 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/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-25T15:59:47.933Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 531 File: src/components/templates/agent-connectors/_usage-granolamcp.mdx:18-48 Timestamp: 2026-03-25T15:59:47.933Z Learning: In `src/components/templates/agent-connectors/_usage-*.mdx` usage template files, the code snippets are intentionally directional/illustrative and are meant to demonstrate the expected call sequence, not production-ready runnable code. When reviewing these files, do not flag missing `try/except` (Python) or `try/catch` (JS/TS) error handling solely because the snippet omits it—focus on whether the call sequence/pattern is conveyed clearly. ``` **Applied to files:** - `src/components/templates/agent-connectors/_usage-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:38:27.783Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T15:06:49.617Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T03:34:41.147Z</summary>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 thecomponent. 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/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T18:41:00.639Z</summary> ``` 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/_usage-tableau.mdx` - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:37:47.033Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:26:39.422Z</summary> ``` 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-tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-13T03:44:23.786Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:20:46.903Z</summary> ``` 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. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-26T07:18:51.377Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-25T10:15:02.544Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 529 File: src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx:188-190 Timestamp: 2026-03-25T10:15:02.544Z Learning: In scalekit-inc/developer-docs, the Aside note in `src/content/docs/agent-auth/mcp/tool-access-via-mcp.mdx` warning that ChatGPT's beta MCP connector "may not work correctly" and "does not fully implement the MCP specification" is intentional. Real-world developers have reported re-auth loops and inconsistent streamable HTTP behaviour with ChatGPT compared to Claude, even though OpenAI's marketing describes it as "full MCP support". Do not flag or suggest removing this compatibility warning in future reviews. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-01T08:35:26.973Z</summary> ``` Learnt from: srinivaskarre-sk Repo: scalekit-inc/developer-docs PR: 566 File: src/content/docs/agent-auth/user-verification.mdx:55-117 Timestamp: 2026-04-01T08:35:26.973Z Learning: In `src/content/docs/agent-auth/user-verification.mdx` and Agent Auth connected accounts documentation (src/content/docs/agent-auth/**/*.mdx), only Python and Node.js SDK support is currently available for Agent Auth features (including connected accounts magic link creation and user verification). Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for these files. Add Go and Java TabItems once those SDKs support Agent Auth/connected account features. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-22T04:05:02.920Z</summary> ``` Learnt from: AkshayParihar33 Repo: scalekit-inc/developer-docs PR: 623 File: src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx:143-237 Timestamp: 2026-04-22T04:05:02.920Z Learning: In `src/content/docs/agentkit/bring-your-own-connector/using-tool-proxy.mdx`, the MCP tool calling SDK examples (`list_scoped_tools` / `execute_tool`, under the "MCP tool calling" section) only include Node.js and Python tabs because Go and Java SDK support for this functionality is not yet available. Do not require or enforce Go and Java tabs in `<Tabs syncKey="tech-stack">` blocks for MCP tool calling in bring-your-own-connector docs until those SDKs support the feature. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-12T16:29:16.422Z</summary> ``` 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/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-27T16:55:31.608Z</summary> ``` Learnt from: saif-at-scalekit Repo: scalekit-inc/developer-docs PR: 544 File: src/content/docs/cookbooks/daily-briefing-agent.mdx:0-0 Timestamp: 2026-03-27T16:55:31.608Z Learning: In `src/content/docs/cookbooks/daily-briefing-agent.mdx`, the `ensureConnected` (TypeScript) and `ensure_connected` (Python) functions intentionally use a single `if` check (not a `while` loop with re-validation) after the OAuth prompt. This is deliberate, well-tested example code reflecting the actual repo pattern. Do not suggest adding retry loops or post-prompt status re-validation in future reviews of this file. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T14:34:06.246Z</summary> ``` Learnt from: saif-at-scalekit Repo: scalekit-inc/developer-docs PR: 618 File: src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx:66-77 Timestamp: 2026-04-20T14:34:06.246Z Learning: In `src/content/docs/authenticate/manage-users-orgs/hosted-widgets.mdx`, do not flag the absence of an explicit `state`/CSRF validation warning next to the authorization URL examples in the "Signup/login widgets" section. The page already links to `/authenticate/fsa/implement-login/` where that security guidance is covered. Flagging it here is considered out of scope for this page. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-10T10:37:49.873Z</summary> ``` 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:49.873Z Learning: In `src/components/templates/agent-connectors/`, all connector setup MDX files (e.g., _setup-asana.mdx, _setup-clickup.mdx, _setup-confluence.mdx, _setup-googlecalendar.mdx, _setup-intercom.mdx, _setup-monday.mdx, _setup-notion.mdx, _setup-zoom.mdx) intentionally use a single shared redirect URI screenshot (`use-own-credentials-redirect-uri.png` located under `@/assets/docs/agent-connectors/<connector-name>/`) for all redirect URI-related steps, even when steps show different UIs (e.g., Scalekit dashboard vs. the third-party console). Do not flag reuse of this image across multiple steps within the same connector file as an issue. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:29:40.242Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: CLAUDE.md:0-0 Timestamp: 2026-04-20T11:29:40.242Z Learning: Applies to src/content/docs/**/*.{md,mdx} : Every documentation page must include frontmatter with at least: `title` (≤60 chars), `description` (≤160 chars), and `sidebar.label` (1-3 words) ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-13T14:22:37.194Z</summary> ``` Learnt from: Pranesh-Raghu Repo: scalekit-inc/developer-docs PR: 591 File: src/content/docs/reference/agent-connectors/calendly.mdx:47-47 Timestamp: 2026-04-13T14:22:37.194Z Learning: In `src/content/docs/reference/agent-connectors/` MDX files (agent-connector reference pages, e.g., calendly.mdx), the `title` attribute on `<Aside>` components is not required. Do not flag missing `title` props on `<Aside>` components in files under this directory. This is a deliberate exception to the global rule requiring `title` on all `<Aside>` components. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-16T21:02:51.181Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: .cursor/rules/expressive-code.mdc:0-0 Timestamp: 2026-03-16T21:02:51.181Z Learning: Applies to **/*.{md,mdx} : Always add a language identifier to fenced code blocks (e.g., `js` not just bare backticks) ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:29:40.242Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: CLAUDE.md:0-0 Timestamp: 2026-04-20T11:29:40.242Z Learning: Applies to src/content/docs/**/*.{md,mdx} : Use fenced code blocks with language identifiers for all code; never use screenshots of code ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-16T21:02:51.181Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: .cursor/rules/expressive-code.mdc:0-0 Timestamp: 2026-03-16T21:02:51.181Z Learning: Applies to **/*.{md,mdx} : Ensure every code example has a language identifier set via `lang` prop or fenced language id ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Prefer fenced code blocks with language identifiers for all code; never use screenshots of code ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-04-20T11:30:52.410Z</summary> ``` Learnt from: CR Repo: scalekit-inc/developer-docs PR: 0 File: AGENTS.md:0-0 Timestamp: 2026-04-20T11:30:52.410Z Learning: Applies to **/*.{md,mdx} : Use language tabs with clear framework titles for code examples ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 appropriate syntax highlighting language from 200+ supported languages in code blocks ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 consistent Tab labels for multi-language examples: 'Node.js', 'Python', 'Go', 'Java' with TabItem values 'node', 'python'/'py', 'go'/'golang', 'java' ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-13T12:46:55.260Z</summary> ``` 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 'title' attribute in code blocks to show framework names: 'Express.js', 'Flask', 'Gin', 'Spring Boot' ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-01-30T18:18:50.883Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-04T12:47:16.544Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T08:57:12.201Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-02-25T13:04:27.491Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-05T11:29:08.125Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T07:27:56.794Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-09T07:32:38.426Z</summary> ``` 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/agentkit/connectors/tableau.mdx` </details> <details> <summary>📚 Learning: 2026-03-17T16:01:50.487Z</summary> ``` Learnt from: dhaneshbs Repo: scalekit-inc/developer-docs PR: 506 File: src/content/docs/authenticate/fsa/quickstart.mdx:851-853 Timestamp: 2026-03-17T16:01:50.487Z Learning: In the Scalekit Python SDK docs, clarify that LogoutUrlOptions is not exported from the top-level scalekit package __init__.py. The correct import path in code samples or reviews is: from scalekit.common.scalekit import LogoutUrlOptions. Do not flag this import path as incorrect in documentation or code reviews; ensure examples reflect the proper import path to avoid confusion for users. ``` **Applied to files:** - `src/content/docs/agentkit/connectors/tableau.mdx` </details> </details><details> <summary>🪛 LanguageTool</summary> <details> <summary>src/content/docs/agentkit/connectors/tableau.mdx</summary> [style] ~25-~25: This phrase is redundant (‘G’ stands for ‘graphic’). Use simply “PNGs”. Context: ...sualizations** — Download dashboards as PNG images, PDF documents, or Excel crosstab files... (ACRONYM_TAUTOLOGY) </details> </details> </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
Avinash-Kamath
approved these changes
Apr 28, 2026
Collaborator
Author
|
@coderabbitai review |
Contributor
✅ Actions performedReview triggered.
|
Collaborator
Author
|
@coderabbitai approve |
Pranesh-Raghu
dismissed stale reviews from coderabbitai[bot], coderabbitai[bot], and coderabbitai[bot]
All requested changes have been addressed in subsequent commits.
Contributor
✅ Actions performedComments resolved and changes approved. |
This was referenced Apr 28, 2026
Merged
This was referenced May 5, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tableau.ts) with all tools and detailed param descriptions including how to get each required IDTest plan
Preview: https://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/agentkit/connectors/tableau/
Summary by CodeRabbit
New Features
Documentation