Loading...
Loading...
Found 9 Skills
dontbesilent Folder Knowledge Base. Transform users' existing local folders into a knowledge base that Agents can reliably search, archive, and maintain; build a minimal knowledge base when users have no materials, generate a knowledge base navigation when materials exist, and support subsequent functions such as adding new materials, searching for answers, identifying current versions, and checking the health status of the knowledge base. Use this whenever users mention phrases like "build a knowledge base", "my folder is the knowledge base", "let AI understand these files", "put materials into the knowledge base", "find things from the knowledge base", "which file is the latest version", "materials are too messy", "establish a Source of Truth". Users don't need to understand Source of Truth, RAG, or Agent configurations. Folder-based knowledge base for AI agents. Use whenever the user wants to build, populate, query, organize, audit, or connect a local folder as a knowledge base, including source-of-truth navigation and version resolution.
Sets up or repairs the AGENTS.md source-of-truth pattern for any project. Creates a well-structured AGENTS.md with real stack info auto-detected from the project, then wires all AI config satellites (.claude/CLAUDE.md, .github/copilot-instructions.md, .agents/rules/, MEMORY.md) to point to it. Eliminates duplication. Always runs in plan mode — asks before acting. Use this skill whenever the user mentions AGENTS.md, agent config, source of truth for AI rules, setting up Claude/Copilot/Cursor for a project, fixing duplicate AI instructions, or wants to consolidate AI configuration files. Trigger even if the user just says "set up agents" or "fix my AI config".
Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.
Agent Workspace Migration. Organize any project into a long-term maintainable Agent workspace with consistent support for both Claude Code and Codex: audit rule files, identify source-of-truth skills, standardize naming conventions, and generate bridges. Triggers: /dbs-agent-migration, /agent-migration, "migrate to Codex", "migrate to Claude Code", "unify AGENTS.md", "organize skill bridges", "my Agent workspace is messy", "help me unify Claude and Codex" Agent workspace migration. Turn any project into a maintainable Claude Code / Codex dual-host workspace by auditing rule files, establishing source-of-truth skills, normalizing names, and generating bridges. Trigger: /dbs-agent-migration, /agent-migration, "migrate to Codex", "migrate to Claude Code", "fix AGENTS.md", "organize skill bridges"
Scout, pilot, or review Mirage virtual-filesystem tool use for Workbench agents while preserving source-of-truth and public-safety boundaries.
File new notes into the right folder and audit/reorganize folder structure in the user's Obsidian vault, using the `obsidian` CLI and a single source-of-truth map note (`00_Index/Folder_Map.md`) that lives inside the vault. Use this whenever a note needs to be placed, filed, sorted, or moved into the vault; whenever the user asks where a note "belongs" or "should go"; and whenever they want to clean up, reorganize, deduplicate, audit, or restructure vault folders (e.g. orphaned notes, dead-end notes, near-duplicate titles, overlapping folders). Trigger even when the user just says "add this to my vault", "put this somewhere sensible", or "tidy up the cellchat notes" without naming a folder. Requires the Obsidian desktop app to be running.
Promote existing research into a canonical article under `articles/` in a Knowledge Base project (the `knowledge-base` starter pack). Read when a decision has actually been made and the team wants the source-of-truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article. Carries the decision-confirmation gate, the `supersedes:` chain that keeps the evidence trail intact, and the canonical voice. Does not conduct new research — that is the sibling `research-with-sources` skill.
End-to-end recipe for adding Sumsub KYC to a website or web app via the Sumsub WebSDK. TRIGGER when the user asks to "integrate / embed / add Sumsub", "show the KYC widget", "add WebSDK", "verify users with Sumsub on the frontend", supplies an existing levelName they want to plug into a page, or asks how to wire up access tokens / lifecycle events / webhooks for Sumsub verification in an arbitrary project. Covers the whole loop — level setup, server-side access-token signing, snsWebSdk init (vanilla canonical, React recipe), client lifecycle events, token refresh, source-of-truth via webhooks + applicant GET, sandbox testing, go-live checklist. SKIP for building the level/questionnaire/POA-preset payload itself (use the sibling skills), or for backend-only API calls with no frontend (use `sumsub-api-generic`).
Manage resume master versions and customized versions for different companies, positions, and JDs. It is used when users need to save multiple resume versions, compare differences, name files, trace application versions, or maintain the resume fact source. Protect the master version and do not overwrite existing versions or unconfirmed facts.