GitBook (@GitBookIO) / X

GitBook

1,459 posts

GitBook

@GitBookIO

The docs platform for technical teams and AI agents

San Francisco

Joined April 2014

Pinned
GitBook
@GitBookIO
Mar 18
The State of Docs Report 2026 is live — insights from documentation experts across the industry on AI's growing role, how teams are measuring success, and where there are still gaps. Read the full report here: buff.ly/yMjIIsX
GitBook
@GitBookIO
Jul 10
Auto-generated skills are fast. Handwritten ones are precise. The best ones are both — AI drafts the structure, your team adds the judgment.
Addison
@addisonschultz
Jul 10
AI agents are only as good as the context you give them — that's why skill.md files are taking off right now Auto-generating one from your docs is fast but inherits every gap. Writing by hand is precise but slow.
GitBook
@GitBookIO
Jul 7
Your docs have a new audience: AI agents. But many docs sites have problems agents can't work around — client-side rendering, truncated pages, no clean markdown. Invisible to humans, dealbreakers for agents. We built a checker: paste your docs URL, get your AI-readiness score.
GitBook
@GitBookIO
Jul 7
Check your score → buff.ly/2jiLF2M
GitBook
@GitBookIO
Jul 3
76% of docs teams now use AI regularly. But the State of Docs 2026 report makes it clear: the results you get are only as good as the context you give it. We're making it easier to work with agents on docs both people and agents can rely on. Read more: stateofdocs.com/2026/ai-and-do…
GitBook
@GitBookIO
Jul 2
We've revamped the developer tools page in GitBook ✨ More context, better guides, and a faster way to get started with GitBook and agents. Create a developer token, hit our APIs directly — and yes, they work with our skills too. app.gitbook.com/account/develo…
GitBook
@GitBookIO
Jul 1
Using GitBook with @claudeai, @cursor_ai, or @OpenAI? There's a skill for that. Add GitBook skills to work on your docs with one line: 〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️〰️ npx skills add GitBookIO/gitbook-skills
GitBook
@GitBookIO
Jun 30
Your docs already contain everything an agent needs to understand your product. We built a tool to turn that context into something agents can actually use. Paste your docs URL → get a complete SKILL.md, compatible with Claude, Cursor, and 30+ other agents.
GitBook
@GitBookIO
Jun 30
Try it for free: gitbook.com/skill-generator
GitBook
@GitBookIO
Jun 26
GitBook Agent keeps on getting better. Most AI writing tools start from scratch. Agent starts with everything — your team's docs, your writing style, your connected sources, and even works in GitHub, Linear, and Slack.
GitBook
@GitBookIO
Jun 26
See how GitBook Agent can work for your team:
GitBook Agent – A proactive AI collaborator for your docs team
From gitbook.com
GitBook
@GitBookIO
Jun 24
Making your docs AI-ready isn't enough. If your content is outdated, llms.txt and MCP support just means AI agents confidently give users the wrong answer. Our Head of Engineering wrote on why quality still matters most.
GitBook
@GitBookIO
Jun 24
Read the full post here:
Supporting AI standards at GitBook: What OKF, MCP and llms.txt tell us about the future of docs –...
From gitbook.com
GitBook
@GitBookIO
Jun 23
Using @SlackHQ, @github, or @linear? We’re running a webinar today on keeping your GitBook docs up to date from your favorite tools without leaving any context behind. Join us here: gitbook.com/events/channels
GitBook
@GitBookIO
Jun 19
Using update blocks with tags? Visitors on your published site can filter by tag to find exactly what they're looking for — new releases, fixes, improvements, you name it Learn more (and try it yourself!) in our changelog: gitbook.com/docs/changelog
GitBook
@GitBookIO
Jun 17
Want to evolve your documentation skills for 2026? Sarah’s latest post offers a ton of practical advice. Here are the headlines: 🔄 Think in systems, not pages – consistency and relationships are everything 🤔 Get better at judgement than drafting – make the most of your
5 ways to improve your technical writer skills for 2026 | GitBook Blog
From gitbook.com
GitBook
@GitBookIO
Jun 15
The #1 docs challenge for product teams is keeping them up to date. GitBook Channels fixes that — trigger a change request by mentioning @GitBookIO in a thread, without leaving your tools. Join us on June 23rd 👉 gitbook.com/events/channels
GitBook
@GitBookIO
Jun 12
AI changes who reads your docs. It doesn't change who they're for. GitBook Docs Lead Sarah makes the case that even when agents retrieve, summarize, and execute your documentation — there's always a human on the other side of the outcome. Read the full post: