Menu
SkillsMP has collected 22 skills from alexeyshishin/as-skill. Open a skill to review its source and details.
Showing 22 of 22 collected skills.
Enrich Obsidian note frontmatter — fill in the aliases, up, down, other fields without moving the note. Use this skill when the user asks to update/fill in a note's frontmatter, add aliases or links (up/down/other), or enrich a note with links — especially…
Analyze and review notes from the inbox (`00. Входящие`) — inspection and reporting only, no file changes. The output is a list of notes with recommendations for category and action. For actually processing them (tags, links, moving) use…
Processes an arbitrary markdown file (article, web clip, transcript, notes, draft note) and turns it into structured knowledge for an Obsidian base using the PARA methodology. The skill extracts atomic entities (concepts, insights, facts), invents logical…
Process inbox notes in Obsidian. Use this skill when the user asks to process notes from the `00. Входящие` folder — updating tags, adding aliases, creating links to existing notes (people, MOCs, knowledge), moving them to the right folder per the PARA…
Refactor lecture notes in Obsidian — extract concepts, definitions, and theorems from lecture notes into separate notes, turn the lecture into a "table of contents" with links, update links to the discipline MOC. Use this skill when the user asks to process,…
Refactor a large Obsidian note — split it into atomic/thematic notes while preserving wikilinks in the original. Use this skill when the user asks to split, divide, or refactor a specific note. The skill creates child notes, inserts [[links]] into the…
Offload an Obsidian hub note that too many notes link to (an in-degree tangle). The main signal of a tangle is a high in-degree (tens to hundreds of incoming links); out-degree is secondary. The skill creates sub-MOCs under the hub's existing categories and…
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman…
Defragment and re-actualize a project memory bank (the .assistant/ knowledge base + the project's auto-memory). Reads everything that changed in the repo since the last defrag, finds where the memory bank has gone stale or accumulated amendment-on-amendment…
Maintains a lightweight, always-current "project encyclopedia" in `.memory-bank/` — capturing architecture, stack, conventions, key entities, and active tasks. After each meaningful change, the AI suggests concise updates or explicitly confirms no update is…
Builds a Conventional Commits commit message for the current changes in git. Analyzes the staged diff (or unstaged, if staged is empty), determines type/scope, writes the subject and, if needed, a body. Use when the user wants to "make a commit", "commit the…
Structures a technical tutorial — prerequisites, a "after reading this you'll be able to do X" goal, numbered steps with commands and checks, troubleshooting, cleanup. Doesn't write the full text: it produces a correct skeleton for the author to fill in with…
Implement an already-approved plan from swarm-report/<slug>-plan.md. Routes each task to the executing agent that owns its file scope (frontend / backend / devops / mobile), runs the tests, writes an implementation report. Use AFTER /code-plan, never before.
Find the root cause of a bug or failing test. Spawns 1 debugger subagent that reproduces, ladders hypotheses, isolates with evidence, and applies the minimal fix. Use when a test fails, /code-build reports blocked, or "X stopped working". Does NOT design…
Design a feature before writing code. Spawns planner + skeptic subagents that read the Memory Bank, argue, and write a plan to swarm-report/. Use BEFORE /code-build, for any feature touching 2+ files or with unclear scope. Skip for typos and one-line fixes.
Review a finished change against its plan. Spawns 1 reviewer subagent, reports ship/rework with severity-tagged findings. Use AFTER /code-build.
Critical analysis of Obsidian notes — hybrid search for similar and opposing topics in the knowledge base, identifying contradictions with existing knowledge, reasoned critique of argumentation and coverage completeness. Use this skill whenever the user asks…
Turns an idea, a series of notes, or raw material into an article draft (Habr / Medium / personal blog) — with a TL;DR, a thesis → arguments → example → implication structure, and an authorial voice. Use when "write an article," "shape these thoughts into a…
A content factory — turns a single source into a full content package in one pass. Takes as input a finished article, a video transcript, OR (if there's only a topic) offers to run deep research and assemble a source itself. Output: a 1500–2500 word article,…
A skill for humanizing Russian-language text. Removes signs of AI generation, makes the text feel alive. ALWAYS use this when the user asks to: humanize a text, remove traces of a neural network, make a text lively/natural, rewrite it like a human, humanize…
Turns an idea, a note, or raw text into a ready-to-post Telegram channel post — tight, thesis-first, in the author's voice, within 500-1500 characters. Use when the user wants "write a TG post," "shape this thought for the channel," "short post," "tg post,"…
Builds a Pull Request description from the diff of the current branch against the base branch (main/master). Analyzes all commits, extracts "why / what / how to verify", captures breaking changes. Use when the user wants to "describe the PR", "write a…