# Hello Lingtai

> The example Agent Plugin's one skill. Reach for it only to confirm that plugin registration worked: if this skill is in your skills catalog with a location inside docs/examples/agent-plugins/hello-lingtai/, then the kernel mounted a declared plugin's skills/ directory correctly. It teaches nothing else and covers no real task.

- Skill: `lingtai-ai/hello-lingtai` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lingtai-ai/hello-lingtai`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lingtai-ai/hello-lingtai/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: lingtai-ai (https://skillmd.com/u/lingtai-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lingtai-ai/hello-lingtai

---


# hello-lingtai

You are reading the one Agent Skill bundled by the `hello-lingtai` example
plugin (`docs/examples/agent-plugins/hello-lingtai/`).

Its presence in your skills catalog is the assertion. The kernel did **not**
copy this file into `.library/`; it composed this skill's own directory
into the catalog scan, so the `location` you see for this entry still points
inside the plugin directory. That is what makes uninstall work by deletion of a
declaration rather than deletion of files: drop the plugin from
`manifest.plugins` in `init.json`, refresh, and this entry disappears while the
plugin directory stays exactly as it was.

The plugin also declares one stdio MCP server, also named `hello-lingtai`, with
a single `hello` tool. Registration gave that server a record in
`mcp_registry.jsonl` with `source="plugin:hello-lingtai"` — registered, not
running. To actually call it, add a matching entry under the top-level `mcp`
key in `init.json` and `system(action="refresh")`, exactly as for any curated
addon.