Markdown To Confluence
testdouble/han
Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server.
ADK-TS documentation specialist for Fumadocs MDX pages. An agent skill from BrainDAO/adk-ts.
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BrainDAO/adk-ts adk-docs-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .claude/skills/adk-docs-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .claude/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BrainDAO/adk-ts adk-docs-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .agents/skills/adk-docs-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .agents/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BrainDAO/adk-ts adk-docs-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .cursor/skills/adk-docs-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .cursor/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BrainDAO/adk-ts.git --path .claude/skills/adk-ts-docs-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BrainDAO/adk-ts adk-docs-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .gemini/skills/adk-docs-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .gemini/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BrainDAO/adk-ts adk-docs-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .github/skills/adk-docs-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .github/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BrainDAO/adk-ts adk-docs-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BrainDAO/adk-ts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/adk-ts-docs-writer .opencode/skills/adk-docs-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adk-docs-writer" agent skill from https://github.com/BrainDAO/adk-ts/tree/main/.claude/skills/adk-ts-docs-writer into .opencode/skills/adk-docs-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adk-docs-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
adk-docs-writerADK-TS documentation specialist for Fumadocs MDX pages. An agent skill from BrainDAO/adk-ts.
Adk Docs Writer is an agent skill from BrainDAO/adk-ts. ADK-TS documentation specialist for Fumadocs MDX pages. Use when creating or editing documentation pages in apps/docs/content/docs/, adding new doc sections, discussing docs structure, or updating navigation. Knows Fumadocs components, page archetypes, and navigation registration.
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Markdown. It works with Model Context Protocol and TypeScript. The repository describes itself as: A robust framework for building AI agents with multi-provider LLM support. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f93632d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript, mdx, yaml and json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
npmjs.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Adk Docs Writer loads about 4.9k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,399 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from BrainDAO/adk-ts at commit f93632d, republished under its MIT licence (© BrainDAO). 1,399 words, ~4,868 tokens.
.claude/skills/adk-docs-writer/SKILL.md (or your agent's skills folder).This skill creates and updates documentation pages for the ADK-TS docs site built with Next.js + Fumadocs. It knows the exact component library, frontmatter format, navigation system, and page archetypes used in apps/docs/content/docs/.
meta.json to understand existing navigationadk-style-guide rules (brand, terminology, URLs)All documentation lives in apps/docs/content/docs/ with this layout:
apps/docs/content/docs/
├── agent.md # Root overview
├── meta.json # Root navigation
├── cli/ # CLI reference
├── mcp-servers/ # MCP server documentation
│ ├── iq-ai-servers/ # Built-in MCP servers
│ ├── third-party-wrappers/ # Third-party wrapper servers
│ ├── external-mcps.mdx
│ └── creating-custom-mcps.mdx
└── framework/ # Core framework docs
├── get-started/ # Installation, quickstart
├── agents/ # Agent types, builder, multi-agent
├── tools/ # Tool types, MCP, OpenAPI, auth
├── runtime/ # Event loop, runner, lifecycle
├── session-state-memory/ # Sessions, state, memory
├── artifacts/ # File/data storage
├── callbacks/ # Lifecycle hooks
├── context/ # Context types
├── evaluation/ # Testing, metrics
├── events/ # Event system
├── observability/ # Tracing, metrics
├── plugins/ # Plugin system
└── guides/ # Deployment, integrationsEvery page requires this frontmatter:
---
title: Page Title
description: Brief SEO-friendly description of the page content
---title is required — displayed in sidebar and page header. Keep it clear and keyword-rich, but concise since it shows in the sidebar (e.g., "MCP Tools" not "Overview of MCP Tool Integration")description is required and must be SEO-friendly — this appears in search engine results and social previews. Write a unique 1-2 sentence description with target keywords. Include "ADK-TS" where natural. Example: description: Connect your ADK-TS agent to any MCP server — built-in, external, or custom.icon in page frontmatter — icons go in meta.json onlyWhen creating a new page, you MUST register it in the parent directory's meta.json:
{
"title": "Section Title",
"icon": "IconName",
"pages": ["existing-page", "new-page-slug"]
}my-page.mdx → "my-page")pages array determines sidebar orderBuilding, Bot, Wrench, Play, Database, FileBox, PhoneCall, Layers, FlaskConical, CalendarClock, Eye, Puzzle, BookOpen, TerminalFor new sections (directories), create a meta.json with root: true if it's a top-level section.
Import only the components you actually use on the page.
import { Callout } from "fumadocs-ui/components/callout";
<Callout type="info" title="Optional Title">
Content goes here. Supports **markdown**.
</Callout>;Types: info (default), warn, error, success
import { Cards, Card } from "fumadocs-ui/components/card";
<Cards>
<Card
title="🤖 Card Title"
description="Brief description"
href="/docs/framework/..."
/>
</Cards>;Used for: Related Topics sections, index/overview pages, navigation grids.
Emoji convention: Prefix Card titles with an emoji for visual hierarchy (e.g., "🤖 Agents", "🛠️ Tools", "🧠 Models", "💾 Session"). Exception: MCP server index pages listing many servers use plain titles (e.g., "MCP ABI", "MCP Upbit").
Two patterns are supported:
Pattern A: Steps with markdown headings (simpler, used in quickstarts)
import { Steps } from "fumadocs-ui/components/steps";
<Steps>
### 1. First Step Content for step 1. ### 2. Second Step Content for step 2.
</Steps>;Pattern B: Steps with <Step> wrapper (explicit grouping, used in multi-section guides)
import { Steps, Step } from "fumadocs-ui/components/steps";
<Steps>
<Step>### Generate the Project Content for step 1.</Step>
<Step>### Install Dependencies Content for step 2.</Step>
</Steps>;Used for: Tutorials, quickstarts, setup guides. Use Pattern A for simple linear guides, Pattern B when steps need tighter grouping or when nesting content within steps.
import { Tab, Tabs } from "fumadocs-ui/components/tabs";
<Tabs items={["pnpm", "npm", "yarn"]}>
<Tab value="pnpm">```bash pnpm add @iqai/adk ```</Tab>
<Tab value="npm">```bash npm install @iqai/adk ```</Tab>
</Tabs>;Used for: Package manager alternatives, code variants (Simple/Verbose/Claude Desktop).
import { Mermaid } from "@/components/mdx/mermaid";
<Mermaid
chart={`
graph TD
A[User] --> B[Agent]
B --> C[Tool]
`}
/>;Used for: Architecture diagrams, flow charts.
import { McpToolsList } from "@/components/mcp/mcp-tools-list";
<McpToolsList serverId="upbit" />;Used for: MCP server pages to display available tools. The serverId maps to entries in apps/docs/data/mcp-tools.json.
Used for: Core framework documentation (agents, tools, runtime, etc.)
Reference: apps/docs/content/docs/framework/tools/mcp-tools.mdx
Pattern:
---
title: Feature Name
description: Build and configure feature-name in ADK-TS — setup, usage patterns, and advanced options for TypeScript AI agents.
---
import { Cards, Card } from "fumadocs-ui/components/card";
import { Callout } from "fumadocs-ui/components/callout";
{Opening paragraph explaining what this feature is and why it matters.}
<Callout type="info" title="Key Concept">
Important context or prerequisite knowledge.
</Callout>
## Section 1
Explanation with code examples:
` ` `typescript
import { Feature } from "@iqai/adk";
// example code
` ` `
## Section 2
More detailed content...
## Configuration
| Property | Type | Required | Description |
| -------- | -------- | -------- | ----------- |
| `name` | `string` | Yes | Description |
## Related Topics
<Cards>
<Card
title="🔧 Related Feature"
description="..."
href="/docs/framework/..."
/>
<Card title="📖 Another Topic" description="..." href="/docs/framework/..." />
</Cards>Used for: Individual MCP server documentation in apps/docs/content/docs/mcp-servers/
MCP server pages go in the correct subdirectory:
iq-ai-servers/ — IQ AI built-in servers (@iqai/mcp-* packages)third-party-wrappers/ — wrapped external MCP serversReference: apps/docs/content/docs/mcp-servers/iq-ai-servers/upbit.mdx
Pattern:
---
title: MCP {ServerName}
description: Connect your ADK-TS agent to {ServerName} — installation, configuration, available tools, and integration examples.
---
import { Callout } from "fumadocs-ui/components/callout";
import { Tab, Tabs } from "fumadocs-ui/components/tabs";
- **Package**: [`@iqai/mcp-{name}`](https://www.npmjs.com/package/@iqai/mcp-{name})
- **Provider**: [{ProviderName}]({provider_url})
## Overview
{2-3 sentence description of what the MCP server does and key capabilities.}
<Callout type="info" title="{Relevant context}">
{Important note about the server's behavior or requirements.}
</Callout>
## Getting Started
Install the package:
` ` `bash
pnpm add @iqai/mcp-{name}
` ` `
Use the server in your agent:
<Tabs items={["Simple", "Verbose", "Claude Desktop"]}>
<Tab value="Simple">
` ` `typescript
import { Mcp{Name} } from "@iqai/adk";
const toolset = Mcp{Name}();
const tools = await toolset.getTools();
` ` `
</Tab>
<Tab value="Verbose">
` ` `typescript
import { McpToolset } from "@iqai/adk";
const toolset = new McpToolset({
name: "{Name} MCP Client",
transport: {
mode: "stdio",
command: "npx",
args: ["-y", "@iqai/mcp-{name}"],
env: { ... },
},
});
` ` `
</Tab>
<Tab value="Claude Desktop">
` ` `json
{
"mcpServers": {
"{name}": {
"command": "npx",
"args": ["-y", "@iqai/mcp-{name}"],
"env": { ... }
}
}
}
` ` `
</Tab>
</Tabs>
## Environment Variables
| Variable | Required | Description |
| ------------ | -------- | ----------- |
| `{VAR_NAME}` | Yes/No | Description |
## Available Tools
<McpToolsList serverId="{name}" />
## Integration Example
` ` `typescript
import { Mcp{Name}, LlmAgent } from "@iqai/adk";
const toolset = Mcp{Name}({ env: { ... } });
const tools = await toolset.getTools();
const agent = new LlmAgent({
name: "{name}\_agent",
model: "gemini-2.5-flash",
tools,
});
await toolset.close();
` ` `
## Further Resources
- [{Provider} Documentation]({provider_docs_url})
- [MCP Tools Framework Documentation](/docs/framework/tools/mcp-tools)Used for: Step-by-step tutorials and how-to guides
Reference: apps/docs/content/docs/framework/get-started/quickstart.mdx
Pattern:
---
title: Guide Title
description: Step-by-step guide to building {thing} with ADK-TS — from setup to production-ready TypeScript AI agents.
---
import { Steps } from "fumadocs-ui/components/steps";
import { Tabs, Tab } from "fumadocs-ui/components/tabs";
import { Callout } from "fumadocs-ui/components/callout";
import { Cards, Card } from "fumadocs-ui/components/card";
{Opening paragraph — what the reader will build/learn.}
<Callout title="Prerequisites">
{What the reader needs before starting.}
</Callout>
## Build {The Thing}
<Steps>
### 1. Step Title
{Instructions with code blocks.}
### 2. Step Title
{More instructions.}
<Callout type="warn" title="Important">
{Warning about a common pitfall.}
</Callout>
### 3. Step Title
{Final instructions.}
</Steps>
## Next Steps
<Cards>
<Card title="🚀 Related Guide" description="..." href="/docs/..." />
</Cards>Used for: Section landing pages that link to child pages
Reference: apps/docs/content/docs/mcp-servers/iq-ai-servers/index.mdx
Pattern:
---
title: Section Title
description: Explore ADK-TS {section topic} — overview of available features, components, and integration options for TypeScript AI agents.
---
import { Cards, Card } from "fumadocs-ui/components/card";
import { Callout } from "fumadocs-ui/components/callout";
{1-2 paragraph overview of the section.}
<Callout type="success" title="Key Benefit">
{Why this section matters.}
</Callout>
## Category 1
{Brief description.}
<Cards>
<Card title="🔧 Page Title" description="..." href="/docs/..." />
<Card title="📦 Page Title" description="..." href="/docs/..." />
</Cards>
## Category 2
{Brief description.}
<Cards>
<Card title="🚀 Page Title" description="..." href="/docs/..." />
</Cards>@iqai/adk — never relative pathsAgentBuilder for introductory examples, LlmAgent for advancedgemini-2.5-flash (Gemini is the default LLM). Other supported models: gpt-4.1, claude-sonnet-4-5await toolset.close()Structure pages from simple to complex:
Prefix <Card> titles with a relevant emoji for visual hierarchy (e.g., "🤖 Agents", "🛠️ Tools", "🧠 Models", "💾 Session"). Choose emojis that relate to the topic. Exception: MCP server index pages listing many servers use plain titles without emojis (e.g., "MCP ABI", "MCP Upbit").
Do NOT duplicate cross-cutting content. Best practices, troubleshooting tips, and common errors belong in centralized pages — not scattered across individual concept pages.
Some doc sections have their own dedicated best practices or troubleshooting pages. When writing content for a section, check if one exists in the section's meta.json first. Current section-specific pages:
framework/guides/best-practices.mdxframework/guides/troubleshooting.mdxframework/agents/best-practices.mdxframework/artifacts/best-practices.mdxframework/artifacts/troubleshooting.mdxmcp-servers/best-practices.mdxNew sections should only get their own dedicated page when there's enough section-specific content to justify it. Otherwise, add to the framework-wide guides.
On individual concept pages, keep only content specific to that feature. If you find yourself writing a generic tip (e.g., "always close resources", "handle rate limits"), add it to the appropriate centralized page and link to it from the concept page instead. This prevents the duplication problem where the same advice appears on 5+ pages and drifts out of sync.
Pattern for linking out:
<Callout type="info" title="Best Practices">
See the [best practices guide](/docs/framework/guides/best-practices) for
production recommendations.
</Callout>/docs/framework/guides/The guides/ section contains practical, task-oriented content that spans multiple framework concepts. Use these rules to decide where content belongs:
Belongs in guides/:
guides/deployment/guides/integrations/guides/best-practices.mdxguides/troubleshooting.mdxguides/agent-instructions.mdxDoes NOT belong in guides/:
agents/, tools/, runtime/)Writing guide pages:
End most pages with a Related Topics <Cards> section linking to 2-4 related pages. This helps readers navigate between related concepts.
Every doc page contributes to ADK-TS discoverability. Follow these rules:
title frontmatter: Use clear, keyword-rich titles. Include "ADK-TS" where natural. Example: "MCP Tools" not "Tools Overview".description frontmatter: Write a unique 1-2 sentence description with target keywords. This appears in search results. Example: "Connect your ADK-TS agent to any MCP server — built-in, external, or custom."Use these terms naturally throughout docs (from adk-style-guide):
<Cards> to create link clustersWhen a page URL changes (renamed, moved to a new section, or removed), add a redirect in apps/docs/next.config.mjs so old links don't break.
Redirects are in apps/docs/next.config.mjs in the redirects() function. The config uses pattern-based arrays to keep it compact:
// For a single page move:
{ from: "/docs/old-path", to: "/docs/new-path" }
// For a whole section move (add to the pattern arrays):
// frameworkSections array, mcpServerRedirects array, etc.The site has a custom 404 page (apps/docs/app/not-found.tsx) that shows popular sections. Do NOT redirect all 404s to home — the custom 404 page provides better UX by helping users find what they're looking for. Only add specific redirects for moved/renamed pages.
title and descriptionmeta.json pages array@iqai/adk imports/docs/framework/...)adk-style-guide)© BrainDAO, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/adk-ts-docs-writer of BrainDAO/adk-ts.
Open the folder on GitHubat commit f93632d
Adk Docs Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Adk Docs Writer this skillBrainDAO/adk-ts | 119 | — | ~4.9k | Automated safety check: Pass | MIT | |
| Markdown To Confluencetestdouble/han | 279 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Open Knowledgeojowwalker77/BonsAI | 145 | — | ~5.1k | Automated safety check: Pass | Custom licence | |
| Web Article Extractordongbeixiaohuo/writing-agent | 433 | — | ~740 | Automated safety check: Pass | MIT | |
| Control Chromewxtsky/byob | 142 | — | ~1.5k | Automated safety check: Warn | MIT | |
| Jarvis Setupethanplusai/jarvis | 843 | — | ~2.5k | Automated safety check: Notes | Custom licence |
testdouble/han
Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server.
ojowwalker77/BonsAI
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP.
dongbeixiaohuo/writing-agent
使用隔离的 Chrome DevTools MCP 从博客、新闻、公众号等网页提取正文,返回结构化内容,或保存 Markdown 和远程图片。用户要求提取文章、抓取网页正文、保存为 Markdown、下载文章图片或排查正文选择器时调用。
wxtsky/byob
Control and inspect the user's real Google Chrome through byob's local MCP tools.
ethanplusai/jarvis
A skill your agent uses when helping someone install, configure, or debug a fresh clone of JARVIS (this repo) — especially "the mic doesn't work", "JARVIS says his language systems are down", any…
AeternaLabsHQ/pullmd
Read any web page, document, or YouTube video as clean Markdown using PullMD.
BrainDAO/adk-ts
ADK-TS README specialist. An agent skill from BrainDAO/adk-ts.
BrainDAO/adk-ts
ADK-TS brand voice, terminology, and writing conventions. An agent skill from BrainDAO/adk-ts.
Works with
ADK-TS documentation specialist for Fumadocs MDX pages. An agent skill from BrainDAO/adk-ts. Adk Docs Writer is an agent skill from BrainDAO/adk-ts. ADK-TS documentation specialist for Fumadocs MDX pages.
Adk Docs Writer fits situations like: editing documentation pages in apps/docs/content/docs/; adding new doc sections; discussing docs structure; updating navigation.
Run `npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a claude-code`. Or copy the skill folder (.claude/skills/adk-ts-docs-writer in BrainDAO/adk-ts) into .claude/skills/adk-docs-writer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a codex`. Or copy the skill folder (.claude/skills/adk-ts-docs-writer in BrainDAO/adk-ts) into .agents/skills/adk-docs-writer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BrainDAO/adk-ts --skill adk-docs-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adk-docs-writer, .gemini/skills/adk-docs-writer, .github/skills/adk-docs-writer and .opencode/skills/adk-docs-writer in your project.
SKILL.md names no scripts, command-line tools or credentials: Adk Docs Writer is instructions for the agent only. Our summary lists: Node.js.
SKILL.md names 1 domain. In commands or code: npmjs.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Adk Docs Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.9k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Adk Docs Writer: Markdown To Confluence (testdouble/han, 279 stars), Open Knowledge (ojowwalker77/BonsAI, 145 stars), Web Article Extractor (dongbeixiaohuo/writing-agent, 433 stars) and Control Chrome (wxtsky/byob, 142 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
BrainDAO (a GitHub organization) maintains it in BrainDAO/adk-ts, which has 119 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on June 26, 2026.
Source: BrainDAO/adk-ts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.