Agent skill sync with docs: clarify groups frontmatter with personalization - #6987
Open
mintlify[bot] wants to merge 1 commit into
Open
Agent skill sync with docs: clarify groups frontmatter with personalization#6987mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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
Align the canonical Mintlify skill with the newly documented standalone personalization feature, which changes how the
groupspage frontmatter field behaves.Changes
agent-context/context/skills/mintlify/reference/configuration.md: rewrite thegroupsfrontmatter row so it distinguishes authentication (restricts access) from standalone personalization (controls navigation visibility only; users can still open the page by direct URL).Context
Upstream authoritative changes in the review window (2026-08-14 → 2026-08-15):
groupsin page frontmatter no longer restrict access, only navigation visibility (create/personalization.mdx,deploy/authentication-setup.mdx).Other changes in the window were reviewed and intentionally not synced:
what-is-mintlify/dashboard/permissions— not referenced by the skill.lastUpdatedDatefrontmatter and auto-route fallback — already synced in Agent skill sync with docs: lastUpdatedDate and auto-route fallback #6980.API playgroundcasing, changelog entry) — no behavior change.Validation
Ran from
agent-context/:npm test(node --test): 5 passed, 0 failed.npm run check: "All generated targets are valid and shared references are identical."npm run build: emittedclaude,codex,cursor,kiroworking-tree targets.git diff --check: clean.The existing agent-context sync workflow will distribute the canonical skill to the Codex, Cursor, and Claude plugin repositories after merge.
Note
Low Risk
Documentation-only change in agent skill reference; no runtime or product behavior changes.
Overview
Syncs the canonical Mintlify agent skill with upstream docs on standalone personalization.
In
configuration.md, thegroupsfrontmatter row is rewritten so agents do not treat it as always access-restricting. With authentication,groupsstill restricts access. With standalone personalization, it only affects navigation visibility—users can still open the page via a direct URL.Reviewed by Cursor Bugbot for commit 2a2a120. Bugbot is set up for automated code reviews on this repo. Configure here.