ibl1nk
ibl1nk contains 18 collected skills from bl1nk-bot, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Helps create, edit, and manage custom Qwen Code commands (slash commands). Use this skill whenever the user wants to create a new command, modify an existing command, set up command templates, organize commands into namespaces, or asks about command syntax like @{}, !{}, or {{args}}. Also use when the user mentions "custom commands", "slash commands", "command templates", "command workflows", or wants to automate repetitive AI prompts. If the user has a repetitive task they want to automate with a command, or wants to learn about the commands feature, this skill should be triggered.
Comprehensive writing assistant plugin for novelists and creative writers. Use for story outline management, character tracking, content analysis, Obsidian vault sync, Craft API integration, and Slack notifications. Enables writers to organize plots, analyze narrative structure, detect writing issues, and maintain writing consistency across multiple tools.
Pickle Rick's "God Mode" Implementation Skill. Executes technical plans with rigorous verification. Use when you are ready to write code, run tests, and iterate through implementation phases.No Jerry-work allowed.
Expertise in conducting technical research on codebase tasks and documentation. Use when you need to understand existing implementations, trace data flows, or map codebase patterns.
Expertise in creating detailed, atomic, and safe implementation plans. Use when you need to transform requirements into a step-by-step technical execution strategy.
Activates the Pickle Rick persona. Use this ONLY when the user explicitly requests to start the "Pickle Rick" mode or loop. DO NOT use this for general greetings (e.g., "hi") normal assistance.
Expertise in reviewing implementation plans for architectural soundness, specificity, and safety. Use before implementation to prevent "vague plans" and "messy code."
Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work."
Expertise in reviewing technical research for objectivity, evidence, and completeness. Use to ensure the "Documentarian" standard is met.
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
Expertise in managing Linear tickets locally using Markdown files. Use when you need to create, update, search, or break down features into atomic implementation tickets.
āđāļāļĢāļ·āđāļāļāļĄāļ·āļāđāļāđāđāļāđāļĨāļ°āļāļĢāļ§āļāļŠāļāļāļāļāļāļ§āļēāļĄāļāļĒāđāļēāļāļĄāļ·āļāļāļēāļāļĩāļ āļŠāļēāļĄāļēāļĢāļāļāļąāļāļĢāļđāļāđāļāļāđāļŦāđāļŠāļ§āļĒāļāļēāļĄ āđāļāđāđāļāļāļģāļāļīāļ āļāļĢāļ§āļāļŠāļāļāļāļļāļāļāļāļāļĢāđāļāļāļāļāļāļāļĢāļĢāļāļ° āđāļĨāļ°āđāļāļĨāļĩāđāļĒāļāļāļ·āđāļāļāļ/āļāļ·āđāļāļŠāļāļēāļāļāļĩāđāļāļģāļāļ§āļāļĄāļēāļ āđāļāđāļŠāļģāļŦāļĢāļąāļ: āļāļēāļĢāļāļĢāļ§āļāļŠāļāļāļāļāļāļ§āļēāļĄ, āļāļēāļĢāļāļąāļāļĢāļđāļāđāļāļ, āļāļēāļĢāđāļāđāđāļāļāļģāļāļīāļ, āļāļēāļĢāļāļĢāļ§āļāļŠāļāļāļāļĢāļĢāļāļ°, āđāļĨāļ°āļāļēāļĢāđāļāļĨāļĩāđāļĒāļāļāļ·āđāļāđāļāļāļēāļ°āđāļāļāļāļāļ§āļēāļĄ
āļāļąāļāļāļēāļĢāļāļĢāļīāļāļ āļāļĩāļĒāđāđāļ§āļīāļĢāđāļ āđāļĨāļ°āļāđāļāļĄāļđāļĨāļŠāļģāļāļąāļāļāļāļāđāļĢāļ·āđāļāļāļĢāļēāļ§ āđāļāļ·āđāļāļĢāļąāļāļĐāļēāļāļ§āļēāļĄāļāđāļāđāļāļ·āđāļāļāđāļĨāļ°āļāđāļāļāļāļąāļāđāļāļ·āđāļāļŦāļēāļāļāļāļāļ°āđāļĨ
āđāļāļĩāđāļĒāļ§āļāļēāļāđāļāļāļēāļĢāđāļāļĨāļĩāđāļĒāļāđāļĨāļ°āļŠāļĢāđāļēāļāđāļŦāļĄāđāļĄāļļāļĄāļĄāļāļ āđāļāļĨāļāļāļēāļāļĄāļļāļĄāļĄāļāļāđāļāļĩāļĒāļāđāļāļāđāļāļēāđāļŦāđāđāļāđāļāđāļāļāļāļąāļ āđāļāļīāđāļĄāļāļ§āļēāļĄāļĢāļđāđāļŠāļķāļāđāļŦāļĄāļ·āļāļāļāļĒāļđāđāđāļāļŠāļāļēāļāļāļēāļĢāļāļĢāļīāļ āļŠāđāļāļĨāđāļ āļēāļĐāļēāđāļāđāļāļ āļēāļĐāļēāļāļđāļāđāļĨāļ°āļĄāļĩāļ āļēāļāļĨāļąāļāļĐāļāđāļāļĩāđāļāļąāļāđāļāļ āļāļģāļāļąāļāļāļģāļāļāļīāļāļēāļĒāļāļĩāđāđāļĄāđāļāļģāđāļāđāļ āđāļĨāļ°āļĄāļĩāļāļ§āļēāļĄāļŠāļēāļĄāļēāļĢāļāđāļāļāļēāļĢāļāļąāļāļāļēāļĢāļāļēāļĢāļĄāļāđāļāļĒāđāļēāļāļĒāļīāđāļ āļŠāļēāļĄāļēāļĢāļāļāļąāđāļāļāđāļēāļāļ§āļēāļĄāļĨāļķāļāļĨāļąāļāļŦāļĢāļ·āļāļāļļāļāļĢāļ°āđāļāļīāļāļāļēāļĢāļĄāļāđāļāļĩāđāļāļķāļāļāļđāļāđāļāļāļĒāđāļēāļāđāļāđāļāļŦāļāļēāđāļāļāđāļēāļĒāđāļāđāļĨāļ°āļāļāļ (āļāļļāļāļāļķāļāļāļđāļāļāļāļāļŦāļāđāļē). āđāļāđāļŠāļģāļŦāļĢāļąāļ: āļāļēāļĢāļŠāļĢāđāļēāļāđāļĢāļ·āđāļāļāđāļĨāđāļēāļāļļāļāļāļĨāļāļĩāđāļŦāļāļķāđāļ, āļāļēāļĢāļāļĢāļąāļāđāļāļĨāļĩāđāļĒāļāļĄāļļāļĄāļĄāļāļāļāļēāļĢāđāļĨāđāļēāđāļĢāļ·āđāļāļ, āļāļēāļĢāđāļāļīāđāļĄāļāļ§āļēāļĄāļāļ·āđāļāđāļāđāļāđāļāļāļāļāļāļ.
āļŠāļĢāđāļēāļāđāļĨāļ°āļāļąāļāđāļāļ Miro board āļāļēāļāļāđāļāļĄāļđāļĨāđāļ context.json āļāđāļēāļ Miro MCP â āļĢāļāļāļĢāļąāļ 3 āļĢāļđāļāđāļāļ: Storyboard (timeline āļāļēāļĄāļāļāļ), Corkboard (cluster āļāļąāļ§āļĨāļ°āļāļĢ/āļŠāļāļēāļāļāļĩāđ/plot), Word Count Tracker (Kanban āļŠāļāļēāļāļ°āļāļģ) āđāļāđāļŠāļģāļŦāļĢāļąāļ: /create-board, āļāļēāļĢ visualize āļāļ§āļēāļĄāļāļ·āļāļŦāļāđāļē, storyboard review
āļāļīāļāļāđāļāđāļāļĄāļđāļĨ context.json āļāļąāļ Notion databases āļāđāļēāļ Notion MCP â āļĢāļāļāļĢāļąāļ push āļāļāļāđāļŦāļĄāđ, āļāļąāļāđāļāļāļāļąāļ§āļĨāļ°āļāļĢ, āļāļąāļāļāļķāļ marketing assets āđāļĨāļ°āļāļķāļāļāđāļāļĄāļđāļĨāļĒāđāļāļāļāļĨāļąāļ āđāļāđāļŠāļģāļŦāļĢāļąāļ: /sync-notion, āļāļēāļĢ push episode āļŦāļĨāļąāļ write-episodes āđāļŠāļĢāđāļ, āļāļēāļĢāļāļđ dashboard āļāļ Notion
Expert in storytelling, adaptation, and screenplay structuring. Use for: converting narrative text into screenplay format, splitting stories into 1-60 episodes, and adjusting word counts per episode (800-1000 words for episodes 1-5, 650-900 words for subsequent episodes).
āļŠāļĢāđāļēāļāļāļ·āđāļāļ āļēāļāļĒāļāļāļĢāđāļŠāļąāđāļāļāļĩāđāļāļķāļāļāļđāļāđāļ (4-5 āļāļģ) āđāļĨāļ°āđāļāļ·āđāļāļŦāļēāđāļĢāļīāđāļĄāļāđāļāļāļĩāđāļĄāļĩāļāļēāļĢāđāļāļĨāļĩāđāļĒāļāđāļāļĨāļāļāļĒāđāļēāļāļĄāļēāļ (āđāļĢāļīāđāļĄāļāđāļāļāļĩāđ 30 āļāļ·āđāļ) āđāļāđāļŠāļģāļŦāļĢāļąāļ: āļāļēāļĢāļŠāļĢāđāļēāļāļāļ·āđāļāļ āļēāļāļĒāļāļāļĢāđāļŠāļąāđāļ, āļāļēāļĢāļŠāļĢāđāļēāļāđāļāļ§āļāļīāļāđāļĢāļīāđāļĄāļāđāļāļŠāļģāļŦāļĢāļąāļāļ āļēāļāļĒāļāļāļĢāđāļŠāļąāđāļ, āļāļēāļĢāļāļĨāļēāļāļ āļēāļāļĒāļāļāļĢāđāļŠāļąāđāļ