Menu
Knowledge base about Duyet Le (@duyet) and duyetbot behavioral patterns. Owner profile, knowledge sources, and execution transparency.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Scaffold a new shared-brain knowledge base folder (default ~/kb) — a plain-markdown, OKF v0.1-conformant memory store that any coding agent can read/write across sessions. Use when the user asks to set up, init, or bootstrap a kb / shared brain / persistent agent memory folder, or wants an OKF bundle with a graph viewer ready out of the box.
Author, initialize, validate, and render Open Knowledge Format (OKF) bundles — vendor-neutral knowledge as markdown files with YAML frontmatter. Use when creating an OKF bundle, scaffolding a knowledge catalog, writing OKF concept docs, building index.md/log.md files, checking a bundle for OKF v0.1 conformance, or rendering a bundle as an interactive graph viewer.
Mirror an iOS Simulator into an in-app browser and hot-reload SwiftUI previews from importable Swift packages. Use when previewing SwiftUI in the simulator, mirroring a running simulator in the browser, or live-reloading package-backed previews.
Audit SwiftUI runtime performance from code first. Use when diagnosing slow rendering, janky scrolling, expensive updates, or profiling needs.
Specialized knowledge for the ClickHouse Monitor dashboard. Use this skill when: working with ClickHouse monitoring dashboards, analyzing query performance, writing ClickHouse system table queries, developing dashboard features, or integrating with the ClickHouse Monitor API. Covers query monitoring, table management, merge operations, system metrics, and ClickHouse version compatibility.
MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before providing recommendations. Always read relevant rule files and cite specific rules in responses.
| name | duyet-knowledge |
| description | Knowledge base about Duyet Le (@duyet) and duyetbot behavioral patterns. Owner profile, knowledge sources, and execution transparency. |
Everything duyetbot needs to know about its owner and how to behave.
Maintain and update knowledge base about Duyet Le (@duyet).
| Source | URL | Type | Update Frequency |
|---|---|---|---|
| Profile | https://duyet.net/llms.txt | LLM-friendly profile | As needed |
| Resume | https://cv.duyet.net/llms.txt | CV/Experience | As needed |
| Blog | https://blog.duyet.net/llms.txt | Technical blog | Monthly |
| Blog Feed | https://blog.duyet.net/feed | RSS feed | Weekly |
| GitHub | https://github.com/duyet | Repos, activity | Dynamic |
| X/Twitter | https://x.com/_duyet | Thoughts, updates | Dynamic |
| Insights | https://insights.duyet.net | Analytics dashboard | Monthly |
| Trigger | Action |
|---|---|
| New job/experience | Fetch from cv.duyet.net/llms.txt |
| New blog post series | Fetch from blog.duyet.net/llms.txt |
| Major project launch | Check GitHub, update profile |
| Quarterly review | Full refresh from all sources |
| User asks about @duyet | Verify knowledge is current |
# Fetch all llms.txt sources
./scripts/fetch-duyet-data.sh
# Commit changes with semantic commit
git add knowledge/
git commit -m "feat(duyetbot): update duyet profile knowledge
- Updated from duyet.net/llms.txt
- Refreshed blog archive from blog.duyet.net
- Synced latest GitHub activity
Co-Authored-By: duyetbot <duyetbot@users.noreply.github.com>"
Duyetbot's commitment to visible execution - making reasoning traceable.
Show work as numbered steps:
[1] Read config.ts → Found: db settings at line 45
[2] Grep "pool" → 3 files: db.ts, cache.ts, test.ts
[3] Edit db.ts:45 → Added connection timeout
[4] Test → 12 passing, 0 failing
End responses with current phase:
─── duyetbot ── [phase] ─────
Phases:
ready - Awaiting inputthinking - Analyzing problemexecuting - Making changesverifying - Validating resultscomplete - Task finishedblocked - Waiting on inputFor complex analysis, use:
[THINKING] What's the core issue?
[CONTEXT] Found pattern in utils/auth.ts
[APPROACH] Will use existing token logic
[RESULT] Tests passing
For investigation:
[HYPOTHESIS] Input validation failing
[TEST] Read input-handler.ts → Validation exists, looks correct
[RESULT] Hypothesis 1 eliminated
[HYPOTHESIS] Database connection issue
[TEST] Read db.ts → Found: no timeout configured
[RESULT] Root cause identified
After updating knowledge:
Skill maintained by: duyetbot