feat(update-project-settings): RM-18985 Add project settings skill for PATCH /v2/projects/me by xavierandueza · Pull Request #15 · readmeio/agent-plugins

xavierandueza · 2026-10-12T04:05:49Z

🚥 Resolves RM-18985

🧰 Changes

Reviewer Note - I wouldn't bother reading over the testing logic too much - its just to ensure that the endpoint and instructions here don't drift/when they do we catch it.

Creates the update-project-styling skill - covers everything in PATCH /v2/projects/me so largest one we have. I broke down the changes into different "categories" for each change that could be made.

This one is MUCH more vibe-coded than the others due to the sheer number of things users can do here.

Note -> also made test cases because I want to make sure that long-term the things that we're saying can be done via this skill can continue to be done:
https://linear.app/readme-io/issue/RM-19065/setup-ci

🧬 QA & Testing

See test cases created for this that emulate what we say the user can do -> ran all of those and they all worked just fine.
full intergration testing needs final skill - that will follow up after this one.

greptile-apps · 2026-10-12T04:14:35Z

Confidence Score: 5/5

[Low impact] The PR appears safe to merge based on this incremental review.

_{Reviews (2) · Last reviewed commit: "Revert "chore(skills): sync skills to cl..." · Reviewed by Greptile}

…ification

…tore

This reverts commit f8926b4.

xavierandueza

self-reviewed, LGTM

runnabro

just blocking on the link, thx!

runnabro · 2026-10-12T17:15:30Z

+
+### Give the agent custom knowledge
+
+Set `ai.chat.knowledge.custom_knowledge` to free text the agent should always know, such as a product terminology, target audience notes and more. It is sent in full with every agent request rather than searched, so keep it concise; writes over the length limit are rejected. Set it to `null` to clear it. Style guides exist under the "Docs Audit" feature and are better configured there.


Suggested change

Set `ai.chat.knowledge.custom_knowledge` to free text the agent should always know, such as a product terminology, target audience notes and more. It is sent in full with every agent request rather than searched, so keep it concise; writes over the length limit are rejected. Set it to `null` to clear it. Style guides exist under the "Docs Audit" feature and are better configured there.

Set `ai.chat.knowledge.custom_knowledge` to free text the agent should always know, such as product terminology, target audience notes, and more. It is sent in full with every agent request rather than searched, so keep it concise; writes over the length limit are rejected. Set it to `null` to clear it. Style guides exist under the "Docs Audit" feature and are better configured there.

(agent response)
Applied. 761ded7

confirmed fixed

runnabro · 2026-10-12T17:16:07Z

+
+## Slack AI Writer
+
+The Slack AI Writer drafts documentation changes from Slack threads, opening a ReadMe branch per thread. See [AI Writer](https://docs.readme.com/main/docs/github-ai-writer). It is currently under closed beta, reach out to support@readme.io to request access.


wrong link?

(agent response)
Yes, it pointed to the GitHub AI Writer. The Slack AI Writer is in closed beta and has no public docs page, so I removed the link and kept the note about requesting access through support. 407290a

Good callout.

We want this to point to:

https://docs.readme.com/main/docs/slack-ai-writer

Instead please - that's hidden for now but will be live by the time this merges in.

(agent response)
Linked to the Slack AI Writer page instead. It is hidden for now and will be live before this merges. 011f3e7

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

minhthanhdang

I feel like lots of context about the endpoints should be in MCP tool/endpoint description rather than in skills here.

minhthanhdang · 2026-10-12T22:58:36Z

+### Turn Ask AI on or off
+
+Set `ai.owlbot.enabled`.
+
+The `ai.owlbot.new_experience` is a legacy field - leave as `true` as the legacy experience is deprecated.
+
+Without the AI Booster Pack, Ask AI offers limited customization. The Booster Pack is an add-on: `ai.owlbot.is_paying` reports whether the project has it.
+
+### Choose where Ask AI appears
+
+Set `ai.owlbot.placements` (full array) to any of:
+
+- `header`: a button in the page header
+- `floating`: a floating button on every page, centered at the bottom
+- `in_search`: inside the search modal - this appears as an 'Ask about "{query}"' and with the booster alternative questions will be generated that on selection will be sent to Ask AI.
+
+The API stores placements in the order `header`, `floating`, `in_search`, whatever order you send. `in_search` only renders in the unified search modal (`appearance.navigation.search_modal: unified`).
+
+The default is `header` and `in_search`. An empty array hides every surface while leaving Ask AI enabled. On an enterprise child, placements come from the parent until the child sets its own.
+
+Related settings elsewhere: the Ask AI accent color (`appearance.brand.askai`) and the unified search modal that combines search with Ask AI (`appearance.navigation.search_modal`) are in [appearance](appearance.md).


For example, IMO these should be in endpoint description in MCP, it feels too low-level to be in a skill. Imagine we add a placement option in the future

(agent response)
Agreed on the values. The skill already tells the agent to read the updateProject schema with get-endpoint, so the list of values and the default were duplicates that would drift. I removed them and now point to the schema. I kept only the behaviour the schema doesn't describe: in_search needs the unified search modal, the API stores placements in a fixed order, an empty array hides every surface, and how enterprise children inherit. cb824b7

…chema

xavierandueza · 2026-10-12T23:08:59Z

(agent response)
@minhthanhdang on the wider point: agreed that facts about a single field (allowed values, defaults, read-only, inheritance) belong in the OpenAPI descriptions. That way the MCP tool and the docs stay correct when the API changes. That means editing the API spec, which lives outside this repo, so it would be a follow-up.

This skill is meant to hold what the schema can't say: which field matches a request, how fields affect each other (e.g. in_search only renders in the unified search modal), plan tiers, which settings are dashboard-only, and how to verify a change. It already sends the agent to the schema for exact fields, and the live test suite catches drift in the behaviour it documents.

I fixed the placements example in cb824b7. Other places still repeat values from the schema, so we can trim those the same way.

…oject-settings-skill

xavierandueza added 4 commits October 9, 2026 16:55

chore: update reference to skill from managing-readme-docs

a1ad3df

wip: added ai category

85a38e1

feat(update-project-settings): document every settings category

c6f3369

test(update-project-settings): add live API suite per settings category

90800d6

xavierandueza self-assigned this Oct 12, 2026

greptile-apps Bot reviewed Oct 12, 2026

View reviewed changes

Comment thread tests/update-project-settings/lib/snapshot.mjs Outdated

xavierandueza added 5 commits October 12, 2026 15:17

fix(update-project-settings): tighten tier wording and write-only ver…

186bcf6

…ification

test(update-project-settings): ignore variable IDs when verifying res…

efcc566

…tore

fix(managing-readme-docs): add skill frontmatter

086f045

chore(skills): sync skills to claude, codex, and cursor

f8926b4

Revert "chore(skills): sync skills to claude, codex, and cursor"

35eece4

This reverts commit f8926b4.

xavierandueza commented Oct 12, 2026

View reviewed changes

xavierandueza marked this pull request as ready for review October 12, 2026 12:50

xavierandueza requested review from minhthanhdang, runnabro and rvisek October 12, 2026 12:51

greptile-apps Bot previously approved these changes Oct 12, 2026

View reviewed changes

runnabro requested changes Oct 12, 2026

View reviewed changes

xavierandueza added 2 commits October 13, 2026 04:20

docs(update-project-settings): fix custom knowledge wording

761ded7

docs(update-project-settings): remove wrong Slack AI Writer link

407290a

xavierandueza added 2 commits October 13, 2026 09:24

docs(update-project-settings): link Slack AI Writer docs

011f3e7

fix: slack writer will be in open beta by time this goes live

b3d683d

xavierandueza requested a review from runnabro October 12, 2026 22:26

runnabro approved these changes Oct 12, 2026

View reviewed changes

minhthanhdang reviewed Oct 12, 2026

View reviewed changes

docs(update-project-settings): defer Ask AI placement values to the s…

cb824b7

…chema

chore: remove whitespace only file

aa377cb

xavierandueza changed the base branch from feature/improve-mcp-auth-skill to feature/improve-skills October 13, 2026 01:17

Merge branch 'feature/improve-skills' into feature/rm-18985-update-pr…

e98128e

…oject-settings-skill

xavierandueza merged commit 94dbd59 into feature/improve-skills Oct 13, 2026
1 check failed


		### Give the agent custom knowledge

		Set `ai.chat.knowledge.custom_knowledge` to free text the agent should always know, such as a product terminology, target audience notes and more. It is sent in full with every agent request rather than searched, so keep it concise; writes over the length limit are rejected. Set it to `null` to clear it. Style guides exist under the "Docs Audit" feature and are better configured there.


		## Slack AI Writer

		The Slack AI Writer drafts documentation changes from Slack threads, opening a ReadMe branch per thread. See [AI Writer](https://docs.readme.com/main/docs/github-ai-writer). It is currently under closed beta, reach out to support@readme.io to request access.

Conversation

xavierandueza commented Oct 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧰 Changes

🧬 QA & Testing

Uh oh!

greptile-apps Bot commented Oct 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Confidence Score: 5/5

Uh oh!

Uh oh!

xavierandueza left a comment

Choose a reason for hiding this comment

Uh oh!

runnabro left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

minhthanhdang left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xavierandueza commented Oct 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

xavierandueza commented Oct 12, 2026 •

edited

Loading

greptile-apps Bot commented Oct 12, 2026 •

edited

Loading