rokokol

papers

Find, read and compare scientific papers without spending the conversation's context on them: a shortlist of identifiers for a topic, a bounded digest of one paper by a reading subagent, a comparison of several, and a note in the user's vault only when they say so. Sources: the paper-search MCP server or its CLI (arXiv, PubMed, Semantic Scholar, OpenAlex, Crossref and more). Use when the user asks to find papers on a topic, look up a DOI or arXiv id, summarise or critique a scientific article, compare papers, or write a literature note. Not for a web page, a blog post or a news article, which is a plain fetch. Triggers: papers, paper, preprint, arXiv, DOI, PubMed, literature review, systematic review, meta-analysis, related work, citations, who cites this, state of the art, what does the research say, научные статьи, найди статьи, препринт, обзор литературы, мета-анализ, литература по теме, найди источники, есть ли работы про, что говорят исследования, разбери статью, конспект научной статьи, сравни статьи

Code & Development Listed

versioning

What it is — what a repository says about itself over time: whether it has a version at all, where that version lives, what its changelog looks like in either case, what deserves an entry, and the ritual that cuts a release. Use when writing or reviewing a CHANGELOG entry, adding or removing a VERSION file, deciding whether a repo should carry a version badge, cutting a release or a git tag, or setting either up in a new repo. Triggers: changelog, CHANGELOG.md, version, VERSION, semver, release, git tag, release tag, bump, Unreleased, чейнджлог, версия, релиз, git-тег, тег релиза, что писать в changelog, поднять версию.

Testing & QA Listed

tests

What it is — a standard for tests that mean something when they are green: a verdict no pipe can swallow, logs read even at exit 0, every check watched failing before it is trusted, test-first with a falsification pass behind it, commits granular enough to bisect, and no compatibility shims for a shape that was never released. Use when writing, running or reviewing tests, judging whether a green run or an exit code proves anything, finding the commit that broke a test or the earlier test that pollutes it, deciding what to do about a test that passes and fails on the same code, or setting up testing in a new repo. Triggers: tests, test suite, coverage, TDD, flaky, mock, fixture, golden file, bisect, which commit broke it, test pollution, .only, exit code, pipefail, debugging, mutation, property-based, e2e, quarantine, напиши тест, покрытие, тесты падают, зелёный прогон, нестабильный тест, какой коммит сломал, падает только в общем прогоне, код возврата, отладка, карантин.

Web & Frontend Listed

huix-standard

What it is — a standard for making Nix-flake-first Linux repos installable on any distribution without Nix: a canonical install.sh (flag grammar, version flag, uninstall by manifest, a dependency preflight that never installs anything), tab completion for the installer, and docker-based distro tests that run the installer's own printed guidance, with a badge per distribution. Born in the huix family. Use when adding non-Nix install support to a repo, writing or extending an install.sh or its --uninstall, adding installer completions or distro tests, or bringing a repo up to the huix family standard; version numbers and changelogs belong to the versioning skill, CI workflow doctrine to the ci skill. Triggers: install.sh, install.sh --uninstall, install manifest, dependency preflight, distro tests, huix, huix standard, установщик, установка без nix, дистрибутивы, тесты на дистрибутивах.

companion

TEMPLATE: rewrite this whole field for your own assistant. Who it is, who the user is, and what the two of them have worked out about each other: the persona, its voice, and the two dossiers, kept out of the always-loaded rules so they cost nothing during technical work. Use when the talk stops being about the task and turns to the two of them — the user says something about himself, his tastes or his habits, tells the assistant how to look, sound or behave, mentions its appearance or character, asks what it knows or remembers about him, edits either dossier, drops a fact about either of them worth keeping, or is simply after support rather than a solution. Describe the situations you actually find yourself in, in the languages you type in, rather than interview questions nobody asks.

Code & Development Listed

ai-commit-trailers

AI disclosure and submission safety for commits, pushes, issues, pull requests, PR reviews, comments, and discussions: Assisted-by / Generated-by trailers, upstream requirements, and mandatory user review before publishing. Use before any commit or action that publishes content as the user, when writing or reviewing a CONTRIBUTING/AI policy, before contributing to a third-party repo, when AI contribution rules are unclear, or when asked about Co-authored-by / Signed-off-by / Generated-by. Triggers: commit, push, pull request, issue, PR review, comment, Assisted-by, Generated-by, Co-authored-by, Signed-off-by, закоммить, коммит, запушь, пуш, открой PR, пулреквест, открой ишью, оставь комментарий, ответь в ишью, ревью PR, смёрджи, раскрытие ИИ, подпись коммита

ci

What it is — a standard for writing CI that stays green for the right reasons: GitHub Actions conventions, pinned toolchains instead of registry-fate lookups, weekly cascades that land dependency bumps and vendored checkers only on green, external-fate jobs kept off pull requests, and falsifiable checks proven able to fail. Use when writing, reviewing or checking any CI workflow, when pushing to a repository that has CI and after the push (ci.sh watch follows the runs to a verdict), when asked whether CI passed or why it went red, when adding badges, setting up dependency auto-updates, deciding what gates a PR, debugging a CI failure that appeared without a code change, or starting CI for a new repo. Triggers: CI, GitHub Actions, workflow, pipeline, badge, cron, dependabot, vendor-sync, vendor.lock, vendored file, push, did CI pass, check CI, напиши CI, проверь CI, посмотри пайплайн, запушь, прошёл ли CI, почему упал CI, добавь workflow, бейджи, обнови зависимости в CI.

reflect

Close a working session by turning what it taught into durable memory: atomic facts with evidence, each routed to its single owner — an Obsidian vault core with its folder of fact notes, the project's agent memory, the always-loaded global rules, or a pending list for rules seen once — and applied as ADD, UPDATE, LINK, SUPERSEDE or NOOP without writing what is already written. Also opens a session by reading the project's core back. Use when the user closes or wraps up a session, asks for a reflection or retrospective, asks what the vault knows about the current project, or when a hook reports a compacted session. Triggers: close the session, wrap up, reflect, retrospective, what do we know about this project, start the session, закрываем сессию, проведи рефлексию, подведём итоги, что мы знаем про этот проект, начинаем сессию, рефлексия в фоне

0 Updated 2 days ago

super-productivity

Manage Super Productivity tasks through its Local REST API — list, create, edit, schedule, complete, delete, run the timer, and report tracked time. Use when the user means their own task list in Super Productivity rather than the agent's checklist for the current session: adding a task, rescheduling it or setting a deadline, subtasks, estimates, projects and tags, the backlog, archiving, starting or stopping the timer, or where the time went. Russian triggers: супер продуктивити, запиши в задачи, закинь в тудушку, добавь задачу, что у меня на сегодня, что у меня на завтра, что по планам на неделю, поставь на завтра, перенеси на пятницу, сдвинь дедлайн, разбей на подзадачи, это на полчаса, отметь выполненной, закрой задачу, убери в архив, закинь в бэклог, запусти таймер, останови таймер, сколько я сегодня наработал, сколько времени ушло на