Skip to content
Back to search

tekyous

MarketplaceWorks with Claude CodeGitHub

Tech stack diagrams and recommendations for AI agents: agent skills and a Claude Code plugin for Tekyous, the tech stack builder and developer tools catalogue. Works in Claude Code, Codex, Cursor, Grok Build and more.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tekyous--agent-skills/badge.svg)](/listings/tekyous--agent-skills)

HTML

<a href="/listings/tekyous--agent-skills"><img src="/api/listings/tekyous--agent-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Pick one. Then ask, for example: - **"Draw this project's tech stack, save the image into the repo and add it to the README."** - **"I'm building a booking app for yoga studios and know some Python. What stack should I use?"**

Claude Code: the plugin

/plugin marketplace add tekyous/agent-skills
/plugin install tekyous@tekyous

It adds the Tekyous MCP server and both skills. They start by themselves when you ask for a stack or a diagram, or run them as `/tekyous:tech-stack-recommendation` and `/tekyous:tech-stack-diagram`. Grok Build installs the same plugin: `grok plugin install tekyous/agent-skills`.

Any agent with skills: the skills

npx skills add tekyous/agent-skills

Or copy the folders in [`skills/`](skills) into your agent's skills folder:

| Agent | Project folder | User folder | |---|---|---| | Claude Code | `.claude/skills/` | `~/.claude/skills/` | | Codex | `.agents/skills/` | `~/.agents/skills/` | | Cursor | `.agents/skills/` or `.cursor/skills/` | `~/.cursor/skills/` | | GitHub Copilot | `.agents/skills/` | `~/.copilot/skills/` | | Antigravity | `.agents/skills/` | `~/.gemini/config/skills/` | | Grok Build | `.grok/skills/` | `~/.grok/skills/` | | Z Code | `.zcode/skills/` | `~/.zcode/skills/` | | Cline | `.agents/skills/` | `~/.agents/skills/` | | OpenCode | `.agents/skills/` | `~/.config/opencode/skills/` | | Kilo Code | `.agents/skills/` | `~/.kilo/skills/` | | Qwen Code | `.qwen/skills/` | `~/.qwen/skills/` | | Kiro CLI | `.kiro/skills/` | `~/.kiro/skills/` |

Many agents also read the shared `.agents/skills/` folder, and `npx skills add` knows more than 75 of them.

The skills work with or without the MCP server connected (see [How it works](#how-it-works)).

Any MCP client: the server only

Add `https://mcp.tekyous.dev/mcp` as a remote (streamable HTTP) MCP server. Setup for Claude, Cursor, VS Code with GitHub Copilot, Codex, Antigravity, Grok Build, Z Code and other agents: [tekyous.dev/mcp](https://tekyous.dev/mcp?utm_source=github&utm_medium=readme#setup).

claude mcp add --transport http --scope user tekyous https://mcp.tekyous.dev/mcp   # Claude Code
codex mcp add tekyous --url https://mcp.tekyous.dev/mcp                             # Codex

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 26 lines
  1. {
  2. "name": "tekyous",
  3. "owner": {
  4. "name": "Tekyous",
  5. "email": "contact@tekyous.dev"
  6. },
  7. "metadata": {
  8. "description": "Tekyous plugins for Claude Code: tech stack recommendations, tech stack diagrams and the developer tools catalogue."
  9. },
  10. "plugins": [
  11. {
  12. "name": "tekyous",
  13. "source": "./",
  14. "description": "Choose and draw your tech stack with Tekyous: stack recommendations grounded in a curated tools catalogue, and tech stack diagrams for your README that open editable in the Tekyous builder. Bundles the Tekyous MCP server and two skills.",
  15. "version": "1.1.0",
  16. "category": "development",
  17. "homepage": "https://tekyous.dev/agents",
  18. "tags": [
  19. "tech-stack-diagram",
  20. "tech-stack-recommendation",
  21. "readme",
  22. "mcp"
  23. ]
  24. }
  25. ]
  26. }
README.md · README · 147 lines
  1. # Tekyous agent skills: tech stack diagrams and recommendations for AI agents
  2. Skills and plugins that bring [Tekyous](https://tekyous.dev?utm_source=github&utm_medium=readme), the tech stack
  3. builder and developer tools catalogue, into your coding agent:
  4. - **`tech-stack-recommendation`**: ask which stack or tools to use, and the agent answers from Tekyous's curated
  5. stacks and tools catalogue (scores, pricing, pros and cons, trade-offs), checked against your project's constraints.
  6. - **`tech-stack-diagram`**: ask the agent to draw your project's tech stack. It reads the repository, draws the tools
  7. with their logos, saves the picture and adds it to your README. The picture links to the same diagram in the
  8. [Tekyous stack builder](https://tekyous.dev/builder?utm_source=github&utm_medium=readme), fully editable.
  9. They come as a **Claude Code plugin** and as **skills** for any agent with a shell. Both use the free
  10. [Tekyous MCP server](https://tekyous.dev/mcp?utm_source=github&utm_medium=readme), which needs no sign-in and no API
  11. key.
  12. [![AI SaaS tech stack: tech stack diagram made with tekyous.dev](examples/ai-saas.png)](https://tekyous.dev/builder?utm_source=github&utm_medium=readme#doc=v1.bZJBb4MwDIX_CvJ1cNiVWydN2qROmtTjxMENLs0akiw2bKjivy-0lIZpx5jn9z7bnOHgQosCJQidBtdxUWtsAraQQ0-BtbNQPuYgWgxF1eY12yHuMiF1zFhQnaKwCa7zDOXHGXQdReg9JC2Xl3LGhfji0zB9c85MDWDpRz55qqA239rWivkarcgUqAuuY8IZ2HRN7L7WJzv0cmGDF8eibQNjNeZz_j5ika0ThqelcuOglgKaOmFZQrjzuEemVcx7jGkCcfaQ9aTEBYYxX6QFdnJMOJXBrl4bbLdvKSNT6LUiTiB399KNstfOkPwLKUH7P4g4tGRlAltkkXiee5E9t3HVqcbH0Y6uWYk2Fs0gWq3MopWEYW0WwmUV1VhN1NbOu5lID8G197_BrQ5jcB_vWMJXR0ET55mPYj-zz43JGd16Y7du6q_zVuMv)
  13. *An AI SaaS stack drawn by the Tekyous MCP server. Click it to open the diagram in the builder and edit it.*
  14. ## Install
  15. Pick one. Then ask, for example:
  16. - **"Draw this project's tech stack, save the image into the repo and add it to the README."**
  17. - **"I'm building a booking app for yoga studios and know some Python. What stack should I use?"**
  18. ### Claude Code: the plugin
  19. ```
  20. /plugin marketplace add tekyous/agent-skills
  21. /plugin install tekyous@tekyous
  22. ```
  23. It adds the Tekyous MCP server and both skills. They start by themselves when you ask for a stack or a diagram, or
  24. run them as `/tekyous:tech-stack-recommendation` and `/tekyous:tech-stack-diagram`. Grok Build installs the same plugin:
  25. `grok plugin install tekyous/agent-skills`.
  26. ### Any agent with skills: the skills
  27. ```bash
  28. npx skills add tekyous/agent-skills
  29. ```
  30. Or copy the folders in [`skills/`](skills) into your agent's skills folder:
  31. | Agent | Project folder | User folder |
  32. |---|---|---|
  33. | Claude Code | `.claude/skills/` | `~/.claude/skills/` |
  34. | Codex | `.agents/skills/` | `~/.agents/skills/` |
  35. | Cursor | `.agents/skills/` or `.cursor/skills/` | `~/.cursor/skills/` |
  36. | GitHub Copilot | `.agents/skills/` | `~/.copilot/skills/` |
  37. | Antigravity | `.agents/skills/` | `~/.gemini/config/skills/` |
  38. | Grok Build | `.grok/skills/` | `~/.grok/skills/` |
  39. | Z Code | `.zcode/skills/` | `~/.zcode/skills/` |
  40. | Cline | `.agents/skills/` | `~/.agents/skills/` |
  41. | OpenCode | `.agents/skills/` | `~/.config/opencode/skills/` |
  42. | Kilo Code | `.agents/skills/` | `~/.kilo/skills/` |
  43. | Qwen Code | `.qwen/skills/` | `~/.qwen/skills/` |
  44. | Kiro CLI | `.kiro/skills/` | `~/.kiro/skills/` |
  45. Many agents also read the shared `.agents/skills/` folder, and `npx skills add` knows more than 75 of them.
  46. The skills work with or without the MCP server connected (see [How it works](#how-it-works)).
  47. ### Any MCP client: the server only
  48. Add `https://mcp.tekyous.dev/mcp` as a remote (streamable HTTP) MCP server. Setup for Claude, Cursor, VS Code with
  49. GitHub Copilot, Codex, Antigravity, Grok Build, Z Code and other agents: [tekyous.dev/mcp](https://tekyous.dev/mcp?utm_source=github&utm_medium=readme#setup).
  50. ```bash
  51. claude mcp add --transport http --scope user tekyous https://mcp.tekyous.dev/mcp # Claude Code
  52. codex mcp add tekyous --url https://mcp.tekyous.dev/mcp # Codex
  53. ```
  54. ## How it works
  55. ### `tech-stack-recommendation`
  56. The skill asks for what's missing (the kind of project, your experience, the constraints), asks Tekyous for its
  57. recommendation (`recommend_stack`) and the finalists' profiles (`get_tool`, `search_tools`), and answers with a short
  58. table: the pick per role, why it fits, its pricing and its main trade-off. It then offers a diagram of the result.
  59. **Tekyous grounds the answer; the agent decides.** Tekyous's recommendation follows the rules of its questionnaire for a
  60. project type and an experience level, and the catalogue doesn't list every tool. The skill tells the agent to check
  61. that the picks fit together and fit your constraints, to recommend a better tool even when Tekyous doesn't list it,
  62. and to say where and why it departs from Tekyous's pick.
  63. It calls the MCP tools when they're connected and the same server over curl when they aren't. Without network it
  64. can't check the catalogue, and says so.
  65. ### `tech-stack-diagram`
  66. The skill reads the project's manifests and config (`package.json`, `pyproject.toml`, `requirements.txt`,
  67. `Dockerfile`, `docker-compose.yml`, CI workflows, the README). It writes a small diagram spec: the tools, in a few
  68. groups by role. Then it draws the spec by the first route that works:
  69. 1. **The MCP tools, when the Tekyous server is connected** (the plugin connects it). The agent looks tools up in the
  70. catalogue with `search_tools` and draws with `compose_diagram`.
  71. 2. **curl, when it isn't.** The same server, called over plain HTTPS: no key, no session, the same picture.
  72. 3. **An offline link, when there is no network** (Codex blocks network for shell commands by default). A local
  73. script encodes the spec into a `tekyous.dev/builder#doc=…` link. You open it and export the image in the builder.
  74. Each route ends with a PNG (or, offline, the link) and a README snippet whose picture links to the editable diagram.
  75. The server checks the spec against the Tekyous catalogue: it suggests catalogue slugs for tools drawn as custom ones
  76. and warns about missing pieces or tools that conflict. The agent fixes what it can and draws again.
  77. Tekyous draws a **tech stack**: the tools a project uses and, if you ask, how they connect. It does not draw code
  78. structure, C4 levels, sequence or entity-relationship diagrams.
  79. ## What is sent, and where
  80. - **Sent:** for a diagram, the spec only: tool names, group titles, captions, notes and connector labels. For a
  81. recommendation, the project type, experience level, language and the tools looked up. Never file contents,
  82. environment values or credentials. The skills tell the agent not to open `.env` files or keys.
  83. - **To:** `mcp.tekyous.dev` (the server) and `img.tekyous.dev` (the image). The offline route sends nothing.
  84. - **Stored:** images for 30 days. The diagram itself lives in its link, which anyone holding it can open, so keep
  85. anything private out of names and notes. Calls are logged without IP addresses for 90 days.
  86. Details: [tekyous.dev/privacy](https://tekyous.dev/privacy#mcp-server).
  87. - **Not done:** no API key, no account, no install hooks, no downloaded code run. The only script is
  88. [`doc_link.py`](skills/tech-stack-diagram/scripts/doc_link.py), the offline encoder (Python standard library).
  89. ## What's in this repository
  90. | Path | What it is |
  91. |---|---|
  92. | `skills/tech-stack-recommendation/` | The recommendation skill |
  93. | `skills/tech-stack-diagram/` | The diagram skill: `SKILL.md`, the spec guidance and the offline encoder |
  94. | `.claude-plugin/` | The Claude Code plugin (`plugin.json`) and this repository as its marketplace (`marketplace.json`) |
  95. | `.mcp.json` | The plugin's connection to the Tekyous MCP server |
  96. | `server.json`, `glama.json` | The server's entry in the [MCP Registry](https://registry.modelcontextprotocol.io) and its Glama listing |
  97. | `scripts/sync_design_stack.py` | Copies the server's `design_stack` prompt into the skill, so both give the same guidance |
  98. | `tests/` | Checks the offline links match the server's own byte for byte |
  99. The Tekyous MCP server itself, the catalogue and the renderer are not open source. This repository holds only the
  100. packaging and the instructions, under the MIT licence.
  101. ## Development
  102. ```bash
  103. python3 -m unittest discover tests # offline links match the server's encoder
  104. python3 scripts/sync_design_stack.py --check # the skill's guidance matches the live prompt
  105. claude plugin validate . # the marketplace and plugin manifests
  106. ```
  107. After the server's `design_stack` prompt changes, run `python3 scripts/sync_design_stack.py` and commit the result.
  108. Something broke, or an agent drew or recommended something odd? Open an issue or write to
  109. [contact@tekyous.dev](mailto:contact@tekyous.dev).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.