verstak-ai

@verstak-ai source repo

17 skills
0 followers
19 hours ago last updated

▌
Entry · verstak-ai
Use this skill BEFORE responding to any question that touches: methodology, knowledge graphs, NKS, conceptual frameworks built around vimarsha (open inquiry), kriya (process/practice), holon (boundary), karta (role with motivation), phenomenon (что-то, на что действуют крии — formerly "entity"), estafeta (relay/handoff). Use it when the user references "the graph", "in NKS", "in methodology", "by my notes", "we discussed", "what does the realm say", or asks "what do I think about X" in a context where they have prior recorded thinking. Use it when the user references named concepts that sound like established terminology in their own work — even if you don't recognize the term, the realm probably does. When uncertain — use it; orient is cheap, answering from training data about a topic the realm has worked through is expensive and often wrong.

0
installs
▌
Design · verstak-ai
Use when the user asks to design, architect, or choose the structure/lifecycle of a system, component, or feature and NKS tools are available. Triggers: 'спроектируй', 'давай продумаем', 'архитектура', 'нужен дизайн', 'design', 'let's think through', 'plan the system', 'what should this look like', mentions of 'жц' / 'lifecycle', 'крия' / 'эстафета' / 'холон', or 'записать в NKS' / 'положить в граф' / 'зафиксировать'. Also use at real decision moments — 'we chose X', 'we decided', 'persist this design' — and after elicitation produced an accepted design/spec. Do not use for implementing an already accepted concrete spec, routine bug fixes, repository inspection, or ordinary coding where no structural choice is open.

0
installs
▌
Intake · verstak-ai
Bring EXTERNAL WORD into an NKS realm — the agent-facing shabda-intake. Use whenever the user hands over ANY external text (a post, article, news item, forwarded message, quote, transcript) to be recorded into a realm, not only issues/docs/code. Triggers: 'запиши пост', 'внеси новость', 'добавь в летопись', 'record this post', 'log this news', 'впусти внешнее слово', 'засей граф из issue/доков', 'intake', 'shabda intake'. Source-independent: post, issue, docs, code, conversation enter through an adapter under one discipline — form to node type, epistemic mode by kind of source, provenance source_kind=shabda, dedup, anchor, verify. Distinct from writing (a node from a distinction you already hold), verstakify (derived config) and product-roadmap (composes this with a GitHub adapter). Needs the nks_* MCP tools.

0
installs
▌
Foreman · verstak-ai
Running a crew of doers on one field of work — the shop-floor role that keeps others working and carries what only the owner can decide. Use when the work is too wide for one doer and splits into parallel units each needing its own place: several pull requests, several services, several branches of one migration. Triggers: 'запусти агентов', 'разведи работу', 'следи за агентами', 'кто из них встал', 'собери решения', 'погонщик', 'бригадир', 'run a crew', 'orchestrate agents', 'who is stuck', 'collect the decisions', 'keep them working'. The foreman does not do the craft: it stands up doers, notices the stalled, gathers what needs deciding, relays answers with their reasoning intact, guards the outward bounds, and reports truthfully. Composes collaborate, autonomous, entry. Needs the nks_* MCP tools.

0
installs
▌
Inquiry · verstak-ai
Use this skill for the LIFE of a vimarsha and work with the FIELD of inquiry — not posing one (that's writing), but moving it through its lifecycle: anchoring, resolving, closing, parking, superseding, crystallizing, or attaching it to a bianhua. Triggers: 'разбери вимарши', 'поле вопрошания', 'закрой вимаршу', 'запаркуй вимаршу', 'разреши вопрошание', 'триаж вимарш', 'work the field of inquiry', 'close/park this vimarsha', 'resolve the question', a high dangling-vimarsha count in orient, or session close. Distinct from writing (which poses a vimarsha — genre, name-question) and from assembly (the realm-wide field pass): this skill is the per-vimarsha and field work of carrying questions to a resolution. Needs the nks_* MCP tools.

0
installs
▌
Minding · verstak-ai bundle
The user's mind in the graph — the personal realm @handle/mind; this skill is its memory: recall and write by reflex, not ritual. WRITE when a durable fact about the user surfaces mid-task and serves no single project — their personal machines, their expiries, people, cross-project lessons → @handle/mind (never harness-local memory). A project's servers, pipeline and dated duties are that project's facts — its own realm, never here. A fact about another project → its realm via this realm's contour map. RECALL when the user's own field is in play: 'вспомни', 'что ты знаешь обо мне', 'что у меня есть', 'что на мне', 'где задеплоено', 'do you remember', 'what's on my plate', or a task needs such a fact. 'запомни' → write. 'заведи мне память' → bootstrap. Needs the nks_* MCP tools.

0
installs
▌
Weaving · verstak-ai
Use this skill when doing semantic work on an existing NKS graph: closing lifecycles, writing sense on arrows, splitting kriyas with multiple actors, reconnecting arrows after phenomenon distinctions, or any work where the graph exists structurally but needs semantic completeness. Triggers: 'проткать', 'прошить', 'ткачество', 'weave', 'close lifecycle', 'fix tensions', 'sense на стрелках', references to leaked/relay-gap/orphan tensions, or when nks_orient(lens="tensions") shows structural problems. Also triggers when entry shows a realm with high tension count (large leaked/relay-gap sections in lens="tensions"). Distinct from design: design creates structure from goals, weaving completes structure that already exists.

0
installs
▌
Writing · verstak-ai bundle
Use this skill when writing nodes into an NKS graph — creating phenomena, kriyas, vimarshas, holons, or kartas. Triggers: 'запиши', 'зафиксируй', 'добавь узел', 'создай крию', 'create phenomenon', 'create entity', 'add to graph', 'nks_add', 'положи в граф', or whenever the agent is about to call any nks_add_* tool or nks_batch with creates. Also when unsure which node type, given_as, or modes to pick. Use even for single-node writes — one wrong type propagates through the graph. Distinct from design (plans paths from goals), weaving (repairs existing structure).

0
installs
▌
Assembly · verstak-ai
Use this skill to assemble a realm — the central ritual of the 時-cycle: discern the pattern over a whole field of inquiry and activity and produce 形, the assembly map. Triggers: 'собери реалм', 'сборка', 'пересборка', 'что здесь происходит по сути', 'повестка', 'состояние реалма целиком', 'assemble the realm', 'what's really going on here', 'reassemble', 'map the transformations'. Also use when entry/orient shows a large ungrouped field — many free vimarshas, a wall of top-level kriyas. Distinct from weaving (semantic repair of existing structure), design (building paths from goals), and inquiry (the per-vimarsha lifecycle work). Needs the nks_* MCP tools, especially nks_add_bianhua and lens="bianhua".

0
installs
▌
Feedback · verstak-ai
Session experience becomes something someone can fix — the agent's own word about the skills and tools it just used. Fires by itself when the experience was non-trivial: a rule missed a case, a description promised what the surface does not do, a fix worked for the wrong reason, a step had no way to prove it was done. Triggers: 'фидбэк', 'дай обратную связь', 'feedback', 'запиши, что не сработало', 'скилл подвёл', 'опиши затык', or the end of a session that carried a stumble. Writes into the shared realm @nks/feedback after checking the field for the same thing already said, and places the case inside that field — the only reach the writer has. Composes writing. Needs the nks_* MCP tools.

0
installs
▌
Integrity · verstak-ai
Use for a transformation's graph integrity, for INTEGRATING one surface with another, or for a reverse audit of prose that claims graph-backed leverage. Triggers: 'integrate X with Y', 'integration', 'wire these two together', 'интеграция', 'состыковать', 'связать поверхности', 'integrity check', 'impact analysis', 'what will this change touch', 'проверь на целостность', 'что затронет это превращение', 'claim audit', 'подкреплено ли графом', 'не театр ли'. An integration task starts here, from the graph, before any code. Propagates a bianhua's impact wavefront or checks prose claims against actual graph edges. Distinct from behavioral verification, which uses reality-audit; needs nks_* tools.

0
installs
▌
Autonomous · verstak-ai
Work autonomously in a verstakified repo — the agent's own cycle over its karta's inbox and live channel. Triggers: 'вахта', 'заступай на вахту', 'работай сам', 'автономный цикл', 'on duty', 'stand watch', 'work autonomously', or an autonomous session start where AGENTS.md names an agent karta. Two loops: a cheap duty tact (wake → reason + since-delta → sleep) and an expensive work tact (grasp → mark intent → ship → relay → integrate → reconcile → weave → close). Wake mode, focus and channel are declared, never guessed; the watch begins only once it can speak, not only hear; no mode excuses an empty tact; work ends at integration, not a commit; a behavioral claim is reality-audited before it relays. Composes entry, inquiry, reality-audit, collaborate, writing, weaving. Needs nks_* MCP tools and a verstakified AGENTS.md.

0
installs
▌
Verstakify · verstak-ai bundle
Use when the user asks to verstakify a repo — bootstrap or refresh its AGENTS.md / CLAUDE.md to the verstak standard, apply the NKS methodology conventions, or wire the session-lifecycle rituals (orient-in-NKS on start, push→update-NKS hooks, quality gate, memory guard, CLAUDE.md pointer — @AGENTS.md import, Windows-safe). Triggers: "verstakify", "verstakify this repo", "привести проект к стандарту", "завести/обновить AGENTS.md", "set up AGENTS.md", "bootstrap AGENTS", "apply the meta template", "наведи порядок в конфиге агента". AGENTS.md is a derived view, not hand-written prose: each concern is audited against its source of truth and re-projected when stale, preserving authored judgment; fresh repos ask the user for the authored slots. Needs the nks_* MCP tools for the NKS steps.

0
installs
▌
Collaborate · verstak-ai bundle
Doers agreeing across contours — how one agent hands work to another and gets an answer back. Use when the work in front of you is not wholly yours: a mandate you don't hold, a boundary you don't steward, knowledge another doer has, a sanction only the owner gives. Triggers: 'спроси другого агента', 'передай задачу', 'это не моя зона', 'эскалируй владельцу', 'collaborate', 'ask another agent', 'hand this off', 'escalate to the owner', or a frame arriving on your channel. Two-way: holding your own socket open is part of entering it — also 'мой канал', 'меня не слышно', 'открой сокет', 'undelivered'. Two surfaces: the graph is the record (an anchored, posed_to vimarsha with its 'Answered when'), the channel is only the wake. Composes writing, inquiry, entry. Needs the nks_* MCP tools.

0
installs
▌
Establish MCP · verstak-ai bundle
Reaching the NKS graph when the harness cannot: nks_* MCP tools are absent, MCP registration fails, or the native OAuth experience keeps failing the user. Ships and raises verstak-bridge — a stdio to streamable-HTTP MCP bridge with the full OAuth flow that never answers the harness with silence. Triggers: 'подключи граф', 'подними мост', 'nks тулы недоступны', 'mcp не подключается', 'oauth не проходит', 'oauth отваливается', 'connect to the graph', 'set up NKS MCP', 'raise the bridge', 'MCP tools missing', tool calls timing out while the server is alive, or a harness whose MCP config takes only command plus args. Composes entry (which needs the tools this skill provides) and verstakify (which wires registration into a repo).

0
installs
▌
Reality Audit · verstak-ai
Use after the final material change of a behavior-changing implementation, before reporting verified/done/green, after requirement corrections or prior falsifier failures, and whenever a test/tool command returned nonzero or mixed pass/fail output must be summarized. Triggers: 'reality audit', 'acceptance check', 'prove it works', 'verify the canonical artifact', 'tests passed', 'проверка реальностью', 'проверь канонический артефакт', 'точно работает'. Verify the exact public deliverable with executable falsifiers; scratch artifacts and print-only observations are provisional.

0
installs
▌
Product Roadmap · verstak-ai bundle
Use this skill to build a product roadmap for a GitHub repository — or a multi-repo product (a whole org, or a set of repos forming one product) — derived from its issues and PRs through an NKS reasoning graph. Triggers: 'roadmap from repo', 'build a roadmap from issues', 'roadmap from github', 'roadmap for my org', 'multi-repo roadmap', 'roadmap across repos', 'quick roadmap', 'roadmap teaser', 'собери роадмап из issues/PR', 'роадмап по продукту', 'что в этом репо делать дальше', product-roadmap. Role-plays the maintainer: verified present-state ground, weighted backlog as shabda, directions underway (bianhua), rendered as graph + markdown + local HTML. Composes verstakify, intake, and assembly. Needs the gh CLI and nks_* MCP tools.

0
installs

17 published skills