Skip to content

docs(TSP-1151): add Skills, Files, and Memory documentation for Super GTM#585

Open
claude[bot] wants to merge 1 commit intomainfrom
docs/TSP-1151
Open

docs(TSP-1151): add Skills, Files, and Memory documentation for Super GTM#585
claude[bot] wants to merge 1 commit intomainfrom
docs/TSP-1151

Conversation

@claude
Copy link
Copy Markdown

@claude claude bot commented Apr 10, 2026

Summary

  • Adds a new page get-started/chat/super-gtm-skills-files-memory.mdx covering the three persistent capability areas in Super GTM
  • Skills: Documents all four skill types — built-in, project, user, and agents-as-skills — with descriptions of when and how each is used
  • Files: Covers the persistent file system, file scopes (user vs. project), and how to interpret the filesystem explorer indicators
  • Memory: Explains per-user memory that accumulates across sessions, including the four memory types and how to manage stored memories
  • Updates the Capabilities card on the main super-gtm.mdx page to link to the new page
  • Adds the new page to docs.json navigation under a Super GTM group

Notes

The Notion source page (https://www.notion.so/relevance/Skills-Files-and-Memory-33cef131d5a981548e1ec656d9906133) was not accessible during drafting. The four memory type names (Preferences, Background, Relationships, Processes) are inferred from the GTM context — please verify these against the actual product and update accordingly.

Test plan

  • Verify page renders correctly at /get-started/chat/super-gtm-skills-files-memory
  • Confirm Super GTM nav group appears correctly in sidebar
  • Verify Capabilities card on /get-started/chat/super-gtm links to new page
  • Confirm all headings are sentence case
  • Validate the four memory type names against the actual product spec

Linear: https://linear.app/relevance/issue/TSP-1151/

🤖 Generated with Claude Code

… GTM

Add a new sub-page covering the three persistent capability areas in
Super GTM: skills (built-in, project, user, and agent-as-skills),
the shared file system with conversation and project scopes, and
per-user memory with four memory types. Update the Capabilities card
on the main Super GTM page to link to the new page, and add the new
page to docs.json navigation under a Super GTM group.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@claude claude bot added the docs-drafter Documentation drafted by Claude label Apr 10, 2026
@linear
Copy link
Copy Markdown

linear bot commented Apr 10, 2026

@mintlify
Copy link
Copy Markdown
Contributor

mintlify bot commented Apr 10, 2026

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

Project Status Preview Updated (UTC)
relevanceai 🟢 Ready View Preview Apr 10, 2026, 7:02 AM

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

@github-actions
Copy link
Copy Markdown
Contributor

🎯 Vibe check — get-started/chat/super-gtm-skills-files-memory.mdx

Scores

Dimension Score What's holding it back
🟢 Consistency 9/10 The filesystem explorer bullet list (lines 78–82) is nearly identical to the version in super-gtm.mdx (lines 165–170). This page is the canonical home for that detail, so the duplication is directionally correct — but see the super-gtm.mdx section below for the fix.
🟢 Technical clarity 9/10 No issues found.
🟢 Non-technical clarity 9/10 No issues found.
🟢 Structure 10/10 No issues found.

✨ Overall vibe

Solid new page. The three-section structure (Skills → Files → Memory) is logical, the Tabs for example workflows make the content skimmable without burying it, and the FAQ covers the right questions a beta user would actually have. Tone and component choices match the rest of the Chat docs. Ready to ship with minor attention to the issues flagged on super-gtm.mdx.


🎯 Vibe check — get-started/chat/super-gtm.mdx

Scores

Dimension Score What's holding it back
🟡 Consistency 7/10 Banned word in the page description. Tab title capitalization slip. Filesystem explorer section duplicates the canonical content in the new skills page.
🟢 Technical clarity 9/10 No issues found.
🟢 Non-technical clarity 8/10 The heading hierarchy issue (H3 before any H2) is minor but creates an odd reading flow at the top of the page.
🟡 Structure 8/10 ### What you can do with Super GTM (line 13) is an H3 with no H2 parent, which skips a heading level.

🔧 Issues

  • Line 3 (description frontmatter): "...to unlock an AI super agent..." — "unlock" is a banned word. Replace with something like "Activate Super GTM in Relevance Chat to give your team an AI agent capable of working across your entire go-to-market stack".

  • Line 13: ### What you can do with Super GTM — H3 used as the first heading after the page intro, with no H2 parent. Either promote to ## What you can do with Super GTM or remove the heading and let the <CardGroup> stand on its own (it's self-explanatory).

  • Line 130: <Tab title="API Key"> → sentence case: <Tab title="API key">. "Key" is not a proper noun or acronym.

  • Lines 162–170: The filesystem explorer section (### Filesystem explorer) is nearly verbatim duplicates of lines 74–82 in super-gtm-skills-files-memory.mdx. Per the content standards, don't duplicate — link to the canonical source. Replace this entire subsection with a one-line callout pointing to the detailed page, e.g.:

    See Skills, files, and memory for details on how the filesystem explorer displays file activity.

  • Line 237: [contact support](https://relevanceai.com/support) — CLAUDE.md says always link to /get-started/support rather than an external support URL. Change to [contact support](/get-started/support).


🧩 Component suggestions

  • Lines 85–95 (Configuring CardGroup): Only the "Capabilities" card has an href. "Integrations" and "Agents" cards don't link anywhere. Either add relevant anchors (e.g. href="#integrations" and href="#agents-as-skills") or remove the href from the Capabilities card and let all three be non-navigable descriptors. The current mix looks inconsistent.

✨ Overall vibe

The page covers everything a beta user needs: how to get access, what to connect, and what the approval flow means. The integrations table with tabs (OAuth / API Key / Planned next) is well-structured and easy to scan. Fix the banned word in the description, collapse the duplicate filesystem explorer section, and this is in good shape.


docs.json note

The only change is adding "get-started/chat/super-gtm-skills-files-memory" to the navigation under the existing super-gtm entry. The placement is correct and the new page is properly linked from the navigation.


🔋 Credit usage
Item Count
Files reviewed 2 (.mdx) + 1 (docs.json nav check)
Context pages read 1 (get-started/chat/introduction.mdx)
Total lines processed ~600

Files read:

  • get-started/chat/super-gtm-skills-files-memory.mdx (188 lines)
  • get-started/chat/super-gtm.mdx (238 lines)
  • get-started/chat/introduction.mdx (399 lines)
  • docs.json (grep only — 2 lines returned)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-drafter Documentation drafted by Claude

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants