rokokol
UserLiterature search and paper analysis for an agent: the papers skill and a packaged paper-search-mcp
Categories
Indexed Skills (18)
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: paper-search, as an MCP server or a CLI (arXiv, Semantic Scholar, OpenAlex 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, state of the art, what does the research say, what do my papers say, научные статьи, по моим статьям, найди статьи, препринт, обзор литературы, мета-анализ, литература по теме, найди источники, есть ли работы про, что говорят исследования, разбери статью, конспект научной статьи, сравни статьи
create-readme
What it is — the house rules for a README: structure and tone, what a project does rather than how, no value copied from the code, one paragraph per line with no hard wrapping, no trailing full stop, no section that has its own file, no version a repository does not have, plus a checker that decides the machine-checkable half. Use when writing a README from scratch AND whenever one is edited, reviewed, restructured, or translated — the rules bite hardest on an edit, because a one-word change to a hard-wrapped paragraph reflows every line after it. Also use before adding a badge, a version claim or an admonition to one. Triggers: README, readme.md, badge, admonition, callout, project description, ридми, написать readme, поправь readme, обнови описание проекта, бейджи.
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, напиши тест, покрытие, тесты падают, зелёный прогон, нестабильный тест, какой коммит сломал, падает только в общем прогоне, код возврата, отладка, карантин.
bash-best-practices
A standard for sh and bash utilities and CLI wrappers: one script shape, help as the single source of truth, portability to the bash 3.2 and BSD userland macOS ships, measured pitfalls, the zsh harness, completions kept honest by machine, shellcheck and shfmt doctrine, and check-sh.sh, a travelling checker holding help, docs and completions to the dispatcher. Use when writing, reviewing or refactoring a shell script or CLI wrapper, adding a subcommand, a flag, an exit code or a completion, choosing which bash a script needs, making a script run on macOS, reading a shellcheck or shfmt finding, or when an ad-hoc command misbehaves in the agent's shell. Triggers: bash, sh, shell script, shebang, set -euo pipefail, --help, usage, subcommand, exit code, completion, compdef, shellcheck, shfmt, bash 3.2, macOS bash, mapfile, readlink -f, pipefail, zsh, напиши bash-скрипт, shell-скрипт, почини скрипт, проверь скрипт, добавь флаг, добавь подкоманду, автодополнение, коды возврата, не работает на маке, вывод --help.
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 file, semver, release, git tag, release tag, bump, Unreleased, чейнджлог, версия, релиз, git-тег, тег релиза, что писать в changelog, поднять версию.
skill-authoring
What it is — the house rules for text an agent loads whole into a conversation, a skill or its own instruction file, and check-skill.sh, the gate that checks a skill. Use before any change to a skill — creating one, editing its SKILL.md, a reference or its description, reviewing or installing one — and before changing the agent's instructions. Triggers: skill, SKILL.md, new skill, fix the skill, review this skill, the skill does not load, CLAUDE.md, AGENTS.md, agent instructions, add a rule, скилл, напиши скилл, поправь скилл, отредактируй скилл, проверь скилл, скилл не подгружается, добавь правило, поправь CLAUDE.md
code-comments
What it is — what a comment in code says and what it must not: the reader it is written for, the register it is written in, the moment it must not be anchored to, and the single source of truth it points at rather than restates. Ships check-comments.sh, which reads comments out of the syntax tree and holds them to the machine-decidable half. Use when writing or editing a comment, reviewing a diff that adds one, deciding whether an explanation belongs beside the line at all, converting comments to a simpler register, or setting the rules up in a new repository. Triggers: comment, code comment, inline comment, commented-out code, TODO, FIXME, banner comment, section header comment, docstring, comment style, комментарий, комментарии в коде, закомментированный код, поясни в комментарии, оформи комментарий, нужен ли тут комментарий, стиль комментариев.
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.
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. 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. Triggers: install.sh, install.sh --uninstall, install manifest, dependency preflight, distro tests, huix, huix standard, установщик, установка без nix, дистрибутивы, тесты на дистрибутивах.
contributing
Everything published under the user's GitHub identity, and the homework before it: pushes (own repositories too), issues, PRs, reviews, merges, comments and discussions, each shown and approved one at a time unless a standing per-repository permission covers it; an upstream's contribution policy, templates and CLA or AI rules in one lookup; duplicate search; what changed on the user's own PRs and issues. Use before any push or anything posted on GitHub, when a bug in someone else's project turns up, and when asked about the user's upstream work. Triggers: push this, open a PR, file an issue upstream, leave a comment, reply to the review, approve the PR, merge it, close the issue, fork it, contribute upstream, any duplicates, what's new on my PRs, запушь, пуш, открой PR, пулреквест, заведи ишью, оставь коммент, ответь в ишью, ответь на ревью, одобри PR, смёрджи, смержи, закрой ишью, переоткрой, форкни, апстрим, контрибут, есть ли дубликаты, что там по моим PR, разрешаю пушить
nix-best-practices
A standard for Nix: the scope a with opens, the shape of a module header and where its options live, what a derivation's meta has to say, what a flake.lock must not hold — everything nixfmt, statix and deadnix cannot see and therefore has to be written down — plus check-nix.sh, a travelling checker that holds a tree to it and proves each of its own checks able to fail. Use when writing, reviewing or refactoring Nix: a NixOS or Home Manager module, a package, an overlay, a flake; when deciding where an option or an overlay belongs; when reading a statix or deadnix finding; or when a formatter and the code disagree. Triggers: nix, nixos, flake, flake.lock, nixpkgs, home-manager, mkOption, mkIf, overlay, derivation, mkDerivation, meta, callPackage, nixfmt, statix, deadnix, with pkgs, with lib, inherit, default.nix, useGlobalPkgs, напиши модуль, поправь флейк, добавь опцию, добавь пакет, оверлей, деривация, проверь nix, отформатируй nix, почему пересобирается
ai-commit-trailers
Which AI-disclosure trailer a commit carries — Generated-by, Assisted-by (mostly or partly), or none — what decides between them, and why never Co-authored-by or Signed-off-by for an agent. Use when writing, amending or rebasing a commit. Triggers: commit, commit message, trailer, Assisted-by, Generated-by, Co-authored-by, Signed-off-by, DCO, AI disclosure, закоммить, коммит, сообщение коммита, трейлер, подпись коммита
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.
maintainer-docs
What it is - the convention for repository-wide maintainer rationale in WORKAROUNDS.md, DEVIATIONS.md and PITFALLS.md: which file owns a non-obvious fact, what an entry must preserve, and when the explanation belongs beside the code instead. Use when writing, reviewing, moving or naming one of those files, documenting a workaround, deviation, pitfall, gotcha or surprising invariant, or deciding whether a reason belongs in an inline comment or a dedicated document. Triggers: WORKAROUNDS.md, DEVIATIONS.md, PITFALLS.md, workaround, deviation, pitfall, gotcha, maintainer note, inline comment, workaround documentation, обходное решение, отклонение, ловушка, подводный камень, комментарий в коде.
close-session
Close a working session: save what it taught where the next session will read it, retire what went stale, leave nothing hanging. Triggers: close the session, wrap up, let's call it a day, sum up the work, that's it for today, закрываем сессию, закрывай сессию, закругляемся, на сегодня заканчиваем, подведи итоги, подводим итоги, на сегодня всё
obsidian-cli
Drive a running Obsidian vault from the terminal through the official Obsidian CLI — read and write notes, find a note by name, alias, tag or property, query and summarise the whole link graph, search, manage properties, tags and tasks. Use whenever a request needs vault data or a vault operation rather than an explanation of Obsidian's UI. Triggers: Obsidian, obsidian-cli, vault, note, notes, backlinks, broken links, orphans, aliases, frontmatter properties, tasks in notes, link graph, most linked notes, related notes, path between notes. Russian triggers: обсидиан, волт, вики, заметка, заметки, моя вики, найди в заметках, найди заметку, как называется заметка, поиск по алиасу, создай заметку, обратные ссылки, бэклинки, битые ссылки, сироты, теги заметок, свойства заметки, алиасы, граф заметок, граф связей, связность вики, острова заметок, изолированные заметки, самые цитируемые заметки, связанные заметки, путь между заметками, задачи в заметках
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, scheduling it for a date or rescheduling it, subtasks, estimates, projects and tags, the backlog, archiving, starting or stopping the timer, or where the time went. Russian triggers: супер продуктивити, запиши в задачи, закинь в тудушку, добавь задачу, что у меня на сегодня, что у меня на завтра, что по планам на неделю, поставь на завтра, перенеси на пятницу, разбей на подзадачи, это на полчаса, отметь выполненной, закрой задачу, убери в архив, закинь в бэклог, запусти таймер, останови таймер, сколько я сегодня наработал, сколько времени ушло на
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, закрываем сессию, проведи рефлексию, подведём итоги, что мы знаем про этот проект, начинаем сессию, рефлексия в фоне
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.