docs(asana): resync — expand from 67 to 166 tools

[ravibits]

Summary

• Refreshes the Asana connector documentation to reflect the full 166-tool set (previously 48 tools were in the data file; the connector has been expanded to 166 in scalekit-inc/tool-agent#338).
• Updates asana.ts with all 166 tools covering tasks, projects, sections, teams, users, workspaces, webhooks, custom fields, goals, portfolios, templates, memberships, time tracking, stories, attachments, and allocations.
• Regenerates asana.mdx with current tool count and metadata.

Stub disclosure

_setup-asana.mdx and _section-after-setup-asana-common-workflows.mdx were previously created stubs cloned from the linear template. They were not modified in this PR — existing content is preserved. They still need:

• Real screenshots replacing any {/* TODO: add screenshot ... */} markers.
• Review of connector-specific setup steps for accuracy (URLs, scopes, app registration flow).

Preview link

https://deploy-preview-786--scalekit-starlight.netlify.app/agentkit/connectors/asana/

Test plan

• Open the preview link and verify the page renders.
• Tool list shows 166 tools.
• Verify tool categories are correct (tasks, projects, sections, teams, users, workspaces, webhooks, custom fields, goals, portfolios, templates, memberships, time tracking, stories, attachments, allocations).
• Review _setup-asana.mdx for connector-specific accuracy.
• Confirm Premium/Enterprise-only tools (goals, portfolios, task search, custom fields) are referenced appropriately in the setup guide.

Summary by CodeRabbit

• Documentation
  • Updated the Asana connector quickstart with a new example and refreshed the list of supported actions, including allocations, attachments, custom fields, and follower management.
  • Removed some connector documentation sections and reordered others to better match the current connector flow.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 70815c80-e584-4bed-a02f-83ef822a15fd

📥 Commits

Reviewing files that changed from the base of the PR and between b269a5e and 3ee0518.

📒 Files selected for processing (3)

• src/components/templates/agent-connectors/index.ts
• src/content/docs/agentkit/connectors/asana.mdx
• src/data/agent-connectors/asana.ts

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (15)

**/*.mdx

📄 CodeRabbit inference engine (.cursorrules)

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

Files:

• src/content/docs/agentkit/connectors/asana.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).
• Headings that match a real API parameter, method, or field name
  (e.g., contactID, xero_tenant_id, executeTool) should preserve
  the original casing. Do NOT flag these as sentence-case violations.
• 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: f...

Files:

• src/content/docs/agentkit/connectors/asana.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/asana.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/asana.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 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/asana.mdx

src/content/**/*.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

src/content/**/*.mdx: All documentation must live as MDX files inside src/content/
Every documentation page must have frontmatter with title (≤60 characters), description (≤160 characters), sidebar label, order, and tags
Write documentation in second person using 'you' and 'your application', present tense for descriptions, and imperative for step-by-step instructions
Avoid filler phrases like 'simply', 'just', 'easily' in documentation and be direct
Explain security implications when relevant in documentation
Every code block demonstrating an SDK operation must include all four languages (Node.js, Python, Go, Java) using synced tabs with syncKey='tech-stack'
SDK variable names are fixed and must not be renamed: Node.js uses scalekit, Python uses scalekit_client, Go uses scalekitClient, Java uses scalekitClient

Files:

• src/content/docs/agentkit/connectors/asana.mdx

**/*.{md,mdx,astro,ts}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.{md,mdx,astro,ts}: Use pnpm pretty-quick --staged via pre-commit git hook to auto-format all staged .md, .mdx, .astro, .ts files with Prettier
Run pnpm format to auto-format all .md, .mdx, .astro, .ts files before pushing changes

Files:

• src/content/docs/agentkit/connectors/asana.mdx
• src/components/templates/agent-connectors/index.ts

src/content/docs/agentkit/connectors/**/*.mdx

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Agent connector docs must use the generated workflow via pnpm run sync-agent-connectors and setup/usage/custom sections must be added through component templates

Files:

• src/content/docs/agentkit/connectors/asana.mdx

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

📄 CodeRabbit inference engine (CLAUDE.md)

src/content/docs/**/*.{md,mdx}: All documentation must follow a documentation-first workflow, and any code change must be accompanied by corresponding documentation updates.
Use the exact SDK variable names in all documentation and code examples: Node.js scalekit, Python scalekit_client, Go scalekitClient, and Java scalekitClient.
Most code examples should include Node.js, Python, Go, and Java implementations with consistent variable naming; examples must show both success and error handling paths.
Product documentation for MCP Auth, Agent Auth, Full Stack Auth, Modular SCIM, and Modular SSO must use a journey-focused approach.
All technical content must be validated through testing, API examples must be current and functional, and security implications must be documented where relevant.
Write documentation with clear, skimmable structure: descriptive section titles, short paragraphs, topic sentences, key takeaways near the top, bullets/tables where useful, and bolded important concepts.
Use simple, unambiguous, active, present-tense, second-person language in documentation; avoid jargon, filler words, and insecure patterns such as hard-coded secrets.
Use imperative phrasing for procedures, front-load the action, explain why when useful, prefer examples over theory, and keep one idea per sentence or paragraph.
Use sentence case for all titles and headings, keep titles short and descriptive, make headings describe outcomes, and avoid gerunds when an imperative works better.
Use concise, sentence-case sidebar labels without punctuation; make them outcome- or object-focused and shorter than page titles.
Follow the correct page template for the document type: how-to guides, API references, concept pages, and release notes each have required sections.
Every documentation page must include frontmatter with at least title, description, and sidebar.label, and those values must meet the stated length and navigation requirements.
Opening paragraphs must state ...

Files:

• src/content/docs/agentkit/connectors/asana.mdx

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

📄 CodeRabbit inference engine (CLAUDE.md)

For agentkit docs snippets, verify the current implementation in the external scalekit-developers/agent-auth-examples repository before updating code examples.

Files:

• src/content/docs/agentkit/connectors/asana.mdx

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

📄 CodeRabbit inference engine (CLAUDE.md)

Use the specified code-commenting standards in inline code comments: avoid restating code, explain unidiomatic patterns, document parameters/returns/exceptions for complex logic, and use standard TODO/FIXME/NOTE formats.

Files:

• src/content/docs/agentkit/connectors/asana.mdx

**

⚙️ CodeRabbit configuration file

**: # CLAUDE.md - Scalekit Documentation Guide

Overview

This file is the single source of truth for all documentation standards and AI assistant guidelines in this repository. All documentation must adhere to the rules defined below.

---

Core Principles

Documentation-first development

Every feature must include comprehensive, user-focused documentation. Documentation is not an afterthought but a first-class deliverable that guides implementation. All code changes require corresponding documentation updates.

Git workflow

• Do NOT include Co-Authored-By lines in commit messages
• At the start of a fresh session, before making any changes, ask the user: "Do you want me to cut a new branch or work on the current branch?"
• Never force push (git push --force or git push -f). If a push fails, stop and clearly explain the reason it failed — do not attempt workarounds without user confirmation.
• For commit, push, and PR creation, spawn a subagent using the Haiku model to handle it. The pre-push hook generates large logs and PR creation output adds unnecessary noise to the main session context.
• Once the user confirms local testing works, or explicitly asks to commit and push, commit all changes, push the branch, and open a PR against main. The PR must include:
  • A crisp description of the changes
  • A preview link in the format: https://deploy-preview-{PR_NUMBER}--scalekit-starlight.netlify.app/{path-to-changed-page}/

SDK variable names (critical)

CRITICAL: Use the exact variable names below in all documentation and code examples.

• Node.js: scalekit
• Python: scalekit_client
• Go: scalekitClient
• Java: scalekitClient

Multi-Language SDK Consistency

All code examples MUST include Node.js, Python, Go, and Java implementations with consistent variable naming conventions. Examples must show both success and error handling paths. Security implications must be explained for each implementation....

Files:

• src/content/docs/agentkit/connectors/asana.mdx
• src/components/templates/agent-connectors/index.ts

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

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

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

Files:

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

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

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

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

Files:

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

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

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

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

Files:

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

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

⚙️ CodeRabbit configuration file

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

• Comments that "duplicate" or restate what the code does.
• Missing comments on bug fixes, workarounds, or issue references.
• Missing inline documentation or explanatory comments.
  Code comments are at the author's discretion.

Files:

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

🧠 Learnings (40)

📚 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/asana.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/asana.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/asana.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/asana.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/asana.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/asana.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/asana.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/asana.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/asana.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/asana.mdx

📚 Learning: 2026-05-16T17:25:30.736Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 693
File: src/content/docs/authenticate/mcp/troubleshooting.mdx:170-170
Timestamp: 2026-05-16T17:25:30.736Z
Learning: In this repo’s documentation (.mdx files), external links should be written using plain Markdown link syntax: `[text](url)`. Do not flag links for missing `target="_blank"` or `rel="noopener"` (avoid adding raw HTML anchors just to include those attributes), and keep the approach consistent with existing docs styling.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-04-25T07:22:18.321Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 633
File: src/components/templates/agent-connectors/_setup-heyreach.mdx:12-12
Timestamp: 2026-04-25T07:22:18.321Z
Learning: In this repo’s MDX documentation files, treat `@/...` paths as aliases that resolve to the `src/` directory (e.g., `@/assets/docs/foo/bar.png` -> `src/assets/docs/foo/bar.png`). When reviewing, do not flag `@`-prefixed image (or other asset) paths as broken; instead, verify that the corresponding physical file exists under `src/`.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-04-27T07:13:48.244Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 628
File: src/content/docs/agentkit/tools/scalekit-optimized-tools.mdx:59-102
Timestamp: 2026-04-27T07:13:48.244Z
Learning: In AgentKit documentation MDX files, when showing Python `execute_tool` calls, treat `connection_name` as a supported argument (along with `tool_name`, `tool_input`, `identifier`, and `connected_account_id`). Do not flag `connection_name` as an invalid/unsupported parameter in these Python examples.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-12T09:43:05.227Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 745
File: src/content/docs/agentkit/authentication/troubleshooting.mdx:22-49
Timestamp: 2026-06-12T09:43:05.227Z
Learning: In this repo, for AgentKit documentation pages under `src/content/docs/agentkit/`, do NOT enforce the usual “four-language (Node.js, Python, Go, Java) SDK tabs” requirement. AgentKit pages should include only the Python and Node.js tabs; if Go and Java tabs are missing on these pages, do not flag it during review.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-06T07:23:46.423Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 658
File: src/components/templates/agent-connectors/_section-before-tool-list-xero-common-patterns.mdx:15-63
Timestamp: 2026-05-06T07:23:46.423Z
Learning: In agentkit agent connectors documentation (files under src/components/templates/agent-connectors and src/content/docs/agentkit/connectors), do not require all four language tabs for SDK code examples. These docs may use only the language tabs relevant to the content (e.g., Node.js and Python). This is an exception to the standard multilingual guideline and should be applied consistently across connector docs.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T13:40:40.902Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/content/docs/agentkit/connectors/handwritten-hubspot.mdx:95-126
Timestamp: 2026-05-07T13:40:40.902Z
Learning: For Quickstart code snippets in scalekit-inc/developer-docs connector docs (agentkit connector pages such as src/content/docs/agentkit/connectors/*.mdx), do not require explicit error/non-happy-path handling. Quickstart examples intentionally show only the happy path to reduce noise and help users complete a first working call quickly. In contrast, for more complete, reference-style examples outside of Quickstart flows, missing error-path handling can be flagged.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T13:41:31.574Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/content/docs/agentkit/connectors/handwritten-hubspot.mdx:453-499
Timestamp: 2026-05-07T13:41:31.574Z
Learning: In scalekit-inc/developer-docs, do not require a "what's next"/next-step signal at the end of agent connector documentation pages under src/content/docs/agentkit/connectors/ (for example, src/content/docs/agentkit/connectors/*.mdx). These pages may omit the typical next-step elements such as a frontmatter next link, a LinkCard, or a final forward-pointer paragraph; missing "what's next" sections on these connector pages should not be flagged as an issue.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T16:16:49.698Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/content/docs/agentkit/connectors/datadog.mdx:64-66
Timestamp: 2026-05-07T16:16:49.698Z
Learning: In scalekit-inc/developer-docs connector quickstart pages, do not flag the Step 4 heading text "Authorize and make your first call" as misleading for non-OAuth connectors (e.g., API key connectors). This heading is a standardized template label used intentionally across all connector types, regardless of connectorAuthType.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T16:42:20.842Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/content/docs/agentkit/connectors/confluence.mdx:70-72
Timestamp: 2026-05-07T16:42:20.842Z
Learning: For connector documentation MDX files under `src/content/docs/agentkit/connectors/` (e.g., agentkit connector pages), the `Tool list` section that renders via `<ToolList tools={tools} />` is injected/managed by `scripts/sync-agent-connectors.js`. If a hand-authored or partially hand-authored connector MDX file temporarily lacks the `Tool list` / `<ToolList tools={tools} />` section, do not flag it as a missing/incorrect section issue—it's expected to be re-injected by the generator in a later sync pass.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-13T14:20:54.610Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 690
File: src/content/docs/agentkit/connectors/monday.mdx:74-79
Timestamp: 2026-05-13T14:20:54.610Z
Learning: In connector documentation MDX pages under `src/content/docs/agentkit/connectors/` (e.g., `monday.mdx`, `clickup.mdx`), the “What you can do” capability bullet sections are auto-generated by the repo’s sync scripts from production API data. During code review, do not flag these sections for formatting/content issues or suggest manual rewrites, and treat edits to those bullets as expected only if the change came from rerunning the sync/update process. If a bullet needs to change, the correct path is to update the upstream API data and re-run the sync script, not to hand-edit the generated MDX.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-13T14:21:01.189Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 690
File: src/content/docs/agentkit/connectors/clickup.mdx:74-79
Timestamp: 2026-05-13T14:21:01.189Z
Learning: In connector MDX pages under src/content/docs/agentkit/connectors/ (e.g., clickup.mdx, monday.mdx), the "What you can do" capability bullet sections are auto-generated by the connector sync script (e.g., scripts/sync-agent-connectors.js). During code review, do not flag or require fixes for label/description mismatches or style/formatting issues within those auto-generated bullet lists, because manual edits will be overwritten by the next sync pass.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-21T09:41:24.514Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 712
File: src/content/docs/agentkit/connectors/clickhouse.mdx:2-4
Timestamp: 2026-05-21T09:41:24.514Z
Learning: For connector documentation MDX pages under src/content/docs/agentkit/connectors/ (*.mdx), treat the page `title` field as auto-generated from the upstream API’s `provider.display_name` and not as a manually editable docs field. If there is a branding/casing mismatch in the generated connector page title, do not flag it as a docs issue; instead, require the correction to be made in the upstream API’s `provider.display_name` source.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T16:00:06.233Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/components/templates/agent-connectors/_section-after-setup-gmail-common-workflows.mdx:13-39
Timestamp: 2026-05-07T16:00:06.233Z
Learning: In documentation MDX files under src/components/templates/agent-connectors/ and src/content/docs/agentkit/connectors/, code examples are intentionally simplified. Do not require or flag missing error handling/failure paths (e.g., try/catch, retries, or explicit error returns) in these docs, even if the project’s general guideline expects both success and error paths in code examples.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T16:00:21.950Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/components/templates/agent-connectors/_section-after-setup-google_ads-common-workflows.mdx:10-18
Timestamp: 2026-05-07T16:00:21.950Z
Learning: In AgentKit agent connector documentation code examples located under src/components/templates/agent-connectors/** and src/content/docs/agentkit/connectors/** (MDX files), do not add explicit error handling in the sample code (e.g., no try/catch blocks or rejected-promise branches). These snippets are intentionally “success-path only” to keep the documentation concise, and this is an explicit exception to any general review guideline that requires both success and error paths in every code example.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-07T16:17:26.787Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 660
File: src/content/docs/agentkit/connectors/databricksworkspace.mdx:29-29
Timestamp: 2026-05-07T16:17:26.787Z
Learning: In scalekit-inc/developer-docs connector quickstart MDX pages under src/content/docs/agentkit/connectors/, use ### (H3) headings inside <Steps> components—not ## (H2)—because H2 renders too large. The page-level CSS override `.sl-markdown-content h3 { font-size: var(--sl-text-lg); }` should be kept in the frontmatter `head` block to size the step headings correctly. When reviewing these connector pages, do not flag ### headings inside <Steps> as incorrect.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-21T09:41:24.514Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 712
File: src/content/docs/agentkit/connectors/clickhouse.mdx:2-4
Timestamp: 2026-05-21T09:41:24.514Z
Learning: When reviewing MDX connector pages in `src/content/docs/agentkit/connectors/` (e.g., connector `*.mdx` files), do not treat casing differences in the page frontmatter `title` as a docs issue. The connector `title` is auto-generated by `scripts/sync-agent-connectors.js` from the upstream API’s `provider.display_name`. If `title` casing doesn’t match other fields (like `description`) that use official vendor branding, that mismatch is an upstream data issue—reviewers should note that the upstream `provider.display_name` must be corrected and avoid changing/flagging the docs `title` casing directly.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:02:50.440Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/cloudfaremcp.mdx:34-41
Timestamp: 2026-05-28T03:02:50.440Z
Learning: For auto-synced connector documentation pages in src/content/docs/agentkit/connectors/ (generated by sync-agent-connectors), do not require/flag a missing `title=` attribute on terminal `bash` code blocks that are used for SDK installation instructions (e.g., commands like `npm install scalekit-sdk/node` or `pip install scalekit`). This exception applies specifically to those install-command blocks in connector pages.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:03:25.785Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/cloudfaremcp.mdx:1-10
Timestamp: 2026-05-28T03:03:25.785Z
Learning: In MDX pages under src/content/docs/agentkit/connectors/ (the connector docs auto-generated from the production Scalekit catalog by scripts/sync-agent-connectors.js), do not flag missing `tags` frontmatter as an issue. These pages’ frontmatter is controlled by the sync script; if `tags` is not included by the script, it should not be required manually. Apply this exception to all auto-synced connector pages in that directory.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:03:32.516Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/airopsmcp.mdx:1-10
Timestamp: 2026-05-28T03:03:32.516Z
Learning: For auto-synced connector documentation MDX files under `src/content/docs/agentkit/connectors/` (generated by `scripts/sync-agent-connectors.js`), do not raise a review finding when the MDX frontmatter is missing `tags`. In this directory, `tags` is optional; only ensure the required frontmatter fields per the docs guidelines are present: `title`, `description`, `sidebar.label`, and `sidebar.order` when applicable.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:03:35.312Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/revealedaimcp.mdx:1-10
Timestamp: 2026-05-28T03:03:35.312Z
Learning: For auto-synced connector documentation pages under src/content/docs/agentkit/connectors/ (MDX files generated by scripts/sync-agent-connectors.js from the production Scalekit catalog), do not raise review findings for missing frontmatter fields sidebar.order or tags. These fields are intentionally omitted because they are not emitted by the sync generation output.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:03:51.366Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/sanitymcp.mdx:1-10
Timestamp: 2026-05-28T03:03:51.366Z
Learning: For auto-synced connector documentation pages under src/content/docs/agentkit/connectors/ (generated by scripts/sync-agent-connectors.js), do not require or flag missing `tags` or `order` frontmatter fields. Those fields are not included in the sync script’s output template, and any manual additions would be overwritten on the next sync run. Apply this rule to all MDX connector pages in that directory.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-28T03:04:03.176Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 723
File: src/content/docs/agentkit/connectors/fiscalaimcp.mdx:2-10
Timestamp: 2026-05-28T03:04:03.176Z
Learning: For this repository’s connector documentation MDX pages, do not require or raise an issue for a missing `tags` field in the MDX frontmatter. Only treat these frontmatter fields as required (where applicable): `title` (≤60 chars), `description` (≤160 chars), `sidebar.label` (≤30 chars), and `sidebar.order` when the page is in a directory-based sidebar section with sibling pages. Never flag missing-`tags` on connector MDX pages (including auto-synced ones under `src/content/docs/agentkit/connectors/`).

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-02T10:18:55.267Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 731
File: src/content/docs/agentkit/connectors/scarpflymcp.mdx:51-53
Timestamp: 2026-06-02T10:18:55.267Z
Learning: For auto-synced connector documentation pages under src/content/docs/agentkit/connectors/ (these are generated by scripts/sync-agent-connectors.js), do not raise or flag issues about the toolName passed to QuickstartGenericOauthSection (e.g., scarpflymcp_get_page_url) regarding session dependency or “requires existing session”. These toolName selections are intentionally sourced from the upstream production catalog sync, so treat them as data-driven configuration rather than something that must reference an existing session at code-review time.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-13T08:55:35.702Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 748
File: src/content/docs/agentkit/connectors/twilio.mdx:28-62
Timestamp: 2026-06-13T08:55:35.702Z
Learning: In auto-synced connector documentation pages under `src/content/docs/agentkit/connectors/` (including `twilio.mdx`), treat the quickstart step structure as data-driven output from the production API sync skill/metadata. Do not flag documentation issues merely because a `QuickstartGenericApikeySection` (or the expected “Authorize and make your first call” first-call step) is missing, or because the presence/ordering of the third authorize/first-call step varies—this omission is intentional when it results from the underlying sync metadata.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-13T08:55:41.638Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 748
File: src/content/docs/agentkit/connectors/twilio.mdx:28-62
Timestamp: 2026-06-13T08:55:41.638Z
Learning: For auto-synced connector documentation MDX pages under src/content/docs/agentkit/connectors/ (generated by scripts/sync-agent-connectors.js), do not require or flag a missing "first execute_tool call" step inside the quickstart <Steps> block. The quickstart step count/content is derived from production metadata/skills and is not manually authored. In particular, for Basic Auth connectors (e.g., Twilio), the absence of a QuickstartGenericApikeySection (or equivalent initial-call section) is intentional and should not be treated as a doc error during code review.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-21T08:54:22.951Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 761
File: src/content/docs/agentkit/connectors/lushamcp.mdx:4-4
Timestamp: 2026-06-21T08:54:22.951Z
Learning: For auto-generated connector documentation MDX pages in `src/content/docs/agentkit/connectors/` (generated by `scripts/sync-agent-connectors.js` from the production Scalekit catalog), do not flag the frontmatter `description` as incomplete if it ends with a trailing ellipsis (`...`) due to upstream character limits. This truncation is expected because the description is sourced from the production schema sync; fix it only by updating the upstream provider data and re-running the sync script (not by manually editing the MDX).

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-21T08:54:31.856Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 761
File: src/content/docs/agentkit/connectors/privacymcp.mdx:57-65
Timestamp: 2026-06-21T08:54:31.856Z
Learning: Do not manually add or require security caution/Aside components (e.g., warnings about PAN/CVV2 or card-data handling) directly in auto-synced connector documentation MDX files under src/content/docs/agentkit/connectors/. These pages are regenerated (overwritten) by scripts/sync-agent-connectors.js from the production schema sync, so hand edits will be lost. If a security note is required for a sensitive connector, add it via the sync script templates or upstream data that feeds the sync, not by editing the generated MDX.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-21T08:54:49.675Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 761
File: src/content/docs/agentkit/connectors/stackaimcp.mdx:4-4
Timestamp: 2026-06-21T08:54:49.675Z
Learning: For auto-synced connector documentation pages (MDX) under src/content/docs/agentkit/connectors/—generated by scripts/sync-agent-connectors.js from the production Scalekit catalog—do not raise code review warnings/errors if the frontmatter `description` value exceeds 160 characters. The description text/length is driven by the upstream production schema during the sync; to change the length/content, update the upstream provider data and re-run scripts/sync-agent-connectors.js rather than manually editing the generated MDX.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-06-21T08:54:58.899Z

Learnt from: Pranesh-Raghu
Repo: scalekit-inc/developer-docs PR: 761
File: src/content/docs/agentkit/connectors/mailercloudmcp.mdx:4-4
Timestamp: 2026-06-21T08:54:58.899Z
Learning: For auto-synced connector documentation MDX pages under src/content/docs/agentkit/connectors/ (generated by scripts/sync-agent-connectors.js), do not raise review issues for brand-name casing or spacing inconsistencies between frontmatter fields—description—and the title/sidebar.label fields (e.g., "Mailer Cloud" vs "Mailercloud"). These values are sourced from the upstream production schema sync; if the mismatch is incorrect, make the fix in the upstream provider data and re-run scripts/sync-agent-connectors.js rather than manually editing the generated MDX.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

📚 Learning: 2026-05-16T17:25:30.736Z

Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 693
File: src/content/docs/authenticate/mcp/troubleshooting.mdx:170-170
Timestamp: 2026-05-16T17:25:30.736Z
Learning: In this repo’s documentation (MD/MDX), external links should be written using plain Markdown link syntax: `[text](url)`. Do not flag external links for missing `target="_blank"` or `rel="noopener"`, and avoid converting Markdown links into raw HTML `<a>` tags just to add those attributes, since that would be inconsistent with the established doc pattern.

Applied to files:

• src/content/docs/agentkit/connectors/asana.mdx

🔇 Additional comments (3)

src/content/docs/agentkit/connectors/asana.mdx (1)

66-79: LGTM!

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

192-193: LGTM!

---

101-103: 🎯 Functional Correctness

No breaking changes found for removed Google OAuth exports.

The symbols SectionGoogleOauthVerification and SectionGoogleOauthVerificationCollapsible are not re-exported from src/components/templates/agent-connectors/index.ts, and no files in src/content depend on them. Existing internal templates use relative imports, so this removal is safe.

---

Walkthrough

The agent-connectors index removes two Google OAuth verification section exports and reorders the Xero and Youtube workflow exports. The Asana connector docs update the quickstart tool reference and replace the listed capabilities with allocation and follower operations.

Changes

Connector template exports

Layer / File(s)	Summary
Public export list update src/components/templates/agent-connectors/index.ts	The index module stops re-exporting the Google OAuth verification sections and reorders the Xero and Youtube section exports.

Asana connector docs

Layer / File(s)	Summary
Quickstart and capability list update src/content/docs/agentkit/connectors/asana.mdx	The Asana docs replace the quickstart tool reference and rewrite the capability list around allocations and follower actions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• scalekit-inc/developer-docs#610: Modifies the same connector template index exports in src/components/templates/agent-connectors/index.ts.
• scalekit-inc/developer-docs#663: Also updates the connector template index export surface in the same module.
• scalekit-inc/developer-docs#779: Touches the Google OAuth verification exports that this PR removes.

Suggested reviewers

• saif-at-scalekit
• amitash1912

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: resyncing Asana docs for the expanded 166-tool set.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch connector-docs/asana

• 🛠️ fix frontmatter
• 🛠️ fix internal links

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[netlify]

✅ Deploy Preview for scalekit-starlight ready!

Name	Link
🔨 Latest commit	3ee0518
🔍 Latest deploy log	https://app.netlify.com/projects/scalekit-starlight/deploys/6a3d16bf150af300085c9504
😎 Deploy Preview	https://deploy-preview-786--scalekit-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 46 (🔴 down 2 from production) Accessibility: 98 (no change from production) Best Practices: 92 (no change from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

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