Saif Ali Shaik

Founding Developer Advocate · Bengaluru

docs · DX · CLIs · agent skills · ecosystem

Projects

DevEx Kit

This page is the long guide. The repo README stays short: what you need, how to install, how to start. Source: github.com/saif-shines/devex-kit.

What it is

A set of agent skills for documentation, SDKs, CLIs, MCP servers, and developer go-to-market. You install a plugin or one skill, then type a slash command. The agent follows that skill.

The kit is generic. Scalekit-only docs work lives in skillkit docs-engineering: agent-connector pages, generated sync, and CODEOWNERS escalation.

How to start

Type /ask-devex and state the job. The human starts this skill. The model does not. 

/ask-devex I need to design first-success DX and then write the getting-started docs

The router names the next skill and gives a command you can paste.

Three skills are user-started: ask-devex, docs-contribution-router, create-skill. The rest may start from a description match.

Install options

Claude Code

/plugin marketplace add saif-shines/devex-kit
/plugin install tooling@devex-kit
/plugin install documentation@devex-kit
/plugin install dev-gtm@devex-kit

tooling includes the router. Install that one first if you are unsure.

Any agent

npx skills add saif-shines/devex-kit --yes
npx skills add saif-shines/devex-kit --skill ask-devex --yes
npx skills add saif-shines/devex-kit --list

Do not install a name from in-progress/.

Local clone

git clone https://github.com/saif-shines/devex-kit
/skills load ./plugins/tooling/skills/ask-devex/SKILL.md

Every shipped skill path is plugins/<plugin>/skills/<name>/SKILL.md.

Tiles

Each skill still has a tile.json. Tessl is not a first-class install path. Do not treat tessl as the default.

The three plugins

  • documentation: where a page goes, writing style, cookbooks, sidebar labels
  • tooling: router, SDKs, CLIs, MCP servers, skills, plugins, code style
  • dev-gtm: launch stories and first-success DX

The live human table is in the repo: docs/skills.md.

Example commands

/docs-contribution-router Where does this customer issue go?
/docs-writing-style review mode. [paste draft]
/authoring-cookbooks Readers say this cookbook is hard to follow
/journey-sidebar-labels Reorder this sidebar as an implementation journey
/sdk-craft Design the public API for our TypeScript SDK
/devrel-tooling Build a CLI that scaffolds new projects. Node.js, commander
/mcp-server-craft Design tool schemas for our search API
/create-skill Turn this release checklist into a skill
/devrel-story-craft review mode. Here is a draft launch story
/devrel-dx-craft plan first-success. Choose Sample Application vs Recipe vs Pattern

Adapt a docs site

Optional files in the docs repo:

  • .devex-kit/placement-map.json for the contribution router
  • .devex-kit/style-prompt-block.md for writing style

The skill uses those files when they exist. Do not put Scalekit connector or escalation maps in this kit.

Change the kit

Read CLAUDE.md first. It is the same file as AGENTS.md.

Drafts go in in-progress/. A skill is not shipped until the promotion checklist is done.

npm test
npm run check
npm run changeset
npm run version
dora review plugins/<plugin>/skills/<name> --quick

If dora is missing, use npx @hacksmith/doraval.