Claude Skills by FrkAk

github.com/FrkAk

25 skillsA× 250 installs56 views

BrainstormAExplicit doorway to the Mymir brainstorm subagent. Use only when the user types /mymir:brainstorm directly. For natural-language brainstorm requests (the user describes a net-new project idea), the /mymir skill or the assistant dispatches the brainstorm agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
ComposerAUse when the user types /mymir:composer or /mymir:composer <taskRef>, or asks composer to "run the next task", "ship the backlog", "compose through my ready queue", "loop through mymir tasks", or otherwise requests end-to-end Mymir task delivery (research → plan → implement → propagate, then pick the next task and repeat). Composer dispatches one fresh subagent per phase per task so each phase runs with a clean context window and a focused tool set; the orchestrator itself only picks tasks, h...ai-agentsgogitVotes: 0GitHub stars: 192
Decompose FeatureAExplicit doorway to the Mymir decompose-feature subagent. Use only when the user types /mymir:decompose-feature directly. For natural-language requests to add a new feature or capability cluster to an active project, the /mymir skill or the assistant dispatches the decompose-feature agent via the Task tool. Do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
Decompose TaskAExplicit doorway to the Mymir decompose-task subagent. Use only when the user types /mymir:decompose-task directly. For natural-language requests to split an existing oversize task (the user says "split this task" or composer's oversize handler routes here), the /mymir skill or the assistant dispatches the decompose-task agent via the Task tool. Do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
DecomposeAExplicit doorway to the Mymir decompose subagent. Use only when the user types /mymir:decompose directly. For natural-language decompose requests (the user asks to break a project description into tasks), the /mymir skill or the assistant dispatches the decompose agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
ManageAExplicit doorway to the Mymir manage subagent. Use only when the user types /mymir:manage directly. For natural-language manage requests (strategic review, graph health audit, rebalancing, deep planning, housekeeping), the /mymir skill or the assistant dispatches the manage agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
OnboardingAExplicit doorway to the Mymir onboarding subagent. Use only when the user types /mymir:onboarding directly. For natural-language onboarding requests (the user asks to import an existing repo into Mymir), the /mymir skill or the assistant dispatches the onboarding agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 192
ReviewADispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's `in_review` write, surfaces the verdict to HOTL, stops), and direct mode from the mymir skill on natural-language requests ("review MYMR-N", "review this PR", "review <PR URL>"). Reads `mymir_context depth='review'` for the implementationPlan rendered alongside executionRecord, plan-vs-files drift...code-qualityrustgoVotes: 0GitHub stars: 192
BrainstormAUse when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to onboarding), a Piyaz project already exists with a description, or the user has a complete spec ready (route to decompose).ai-agentsrustgoVotes: 0GitHub stars: 192
Decompose FeatureAUse when the user wants to add a new feature, capability, or cluster of work to an existing active Piyaz project. Triggers: "add a feature for notifications", "decompose this idea into tasks", "I want to plan out the X subsystem", "extend the project with Y", "add Z to the project". Reuses the project's existing categories and tag vocabulary; creates 5 to 20 tasks plus internal edges and edges to existing project tasks. Does NOT change project status. Do NOT use for greenfield project decompo...ai-agentsrustgoVotes: 0GitHub stars: 192
Decompose TaskAUse when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the `oversize-task` flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break <taskRef> into smaller pieces"). Composer dispatches this from its oversize handler. Splits the parent into 2 to N child tasks, rewires every dependency edge touching the parent, and cancels the parent with rationale citing the children...ai-agentsrustgoVotes: 0GitHub stars: 192
DecomposeAUse when a Piyaz project exists with a description but few or no tasks, and the user wants it broken into an implementable graph (project-level decomposition). Triggers: "decompose", "break this down", "create tasks", "turn this into tasks", "give me a task list", "plan out the work", "how should I build this". Do not use when no Piyaz project exists yet (route to brainstorm), the description is too thin to decompose responsibly (route back to brainstorm), the project already has a full task ...ai-agentsrustgoVotes: 0GitHub stars: 192
ManageAUse when the user explicitly wants a deep CTO-mode review of a Piyaz project. Triggers: "strategic review", "audit the project", "rebalance the graph", "what's the health of this project", "deep dive on the dependency graph", "I want a thorough navigation session", "prune orphans", "connect missing edges", "audit blockers", "consolidate categories or tags", "graph health check". Do not use for routine status / next-task / mark-done / refine; those are handled directly by the /piyaz skill.ai-agentsgotestingVotes: 0GitHub stars: 192
OnboardingAUse when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists yet (route to brainstorm), a Piyaz project for this repo already exists (route to manage), or the user has a clean spec but no code (route to decompose).ai-agentsgoswiftVotes: 0GitHub stars: 192
ReviewADispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's `in_review` write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N", "review this PR", "review <PR URL>"). Reads `piyaz_get lens='review'` for the implementationPlan rendered alongside executionRecord, AC evaluation against executionRecord excer...ai-agentsrustgoVotes: 0GitHub stars: 192
BrainstormAUse when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to onboarding), a Piyaz project already exists with a description, or the user has a complete spec ready (route to decompose).ai-agentsrustgoVotes: 0GitHub stars: 192
BrainstormAUse when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to onboarding), a Piyaz project already exists with a description, or the user has a complete spec ready (route to decompose).ai-agentsrustgoVotes: 0GitHub stars: 192
PiyazAUse when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work on / what's next / what's blocked / where they left off, reporting task completion, dispatching work in parallel, or planning a draft task. Also when the user mentions Piyaz by name (e.g. "piyaz, do X") or references a task by its ref (e.g. VLT-9, KRN-153, PXD-31). Works for any project domain (code or data). Do not i...ai-agentsrustgoVotes: 0GitHub stars: 192
BrainstormAExplicit doorway to the Piyaz brainstorm subagent. Use only when the user types /piyaz:brainstorm directly. For natural-language brainstorm requests (the user describes a net-new project idea), the /piyaz skill or the assistant dispatches the brainstorm agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191
ComposerAUse when the user types /piyaz:composer, /piyaz:composer <taskRef>, or /piyaz:composer rework <taskRef|pr-url>, or asks to run the next Piyaz task end-to-end, ship the backlog, compose through the ready queue, or loop through Piyaz tasks until done. Composer researches, refines, plans, implements, reviews, and fixes each task in a loop until the PR is ready, and merges and continues when the user authorizes it. Do NOT invoke for one-off task lookups, status checks, hand-refinement of one task...ai-agentsjavascriptrustVotes: 0GitHub stars: 191
Decompose FeatureAExplicit doorway to the Piyaz decompose-feature subagent. Use only when the user types /piyaz:decompose-feature directly. For natural-language requests to add a new feature or capability cluster to an active project, the /piyaz skill or the assistant dispatches the decompose-feature agent via the Task tool. Do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191
Decompose TaskAExplicit doorway to the Piyaz decompose-task subagent. Use only when the user types /piyaz:decompose-task directly. For natural-language requests to split an existing oversize task (the user says "split this task" or composer's oversize handler routes here), the /piyaz skill or the assistant dispatches the decompose-task agent via the Task tool. Do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191
DecomposeAExplicit doorway to the Piyaz decompose subagent. Use only when the user types /piyaz:decompose directly. For natural-language decompose requests (the user asks to break a project description into tasks), the /piyaz skill or the assistant dispatches the decompose agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191
ManageAExplicit doorway to the Piyaz manage subagent. Use only when the user types /piyaz:manage directly. For natural-language manage requests (strategic review, graph health audit, rebalancing, deep planning, housekeeping), the /piyaz skill or the assistant dispatches the manage agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191
OnboardingAExplicit doorway to the Piyaz onboarding subagent. Use only when the user types /piyaz:onboarding directly. For natural-language onboarding requests (the user asks to import an existing repo into Piyaz), the /piyaz skill or the assistant dispatches the onboarding agent via the Task tool — do not invoke this skill for that path.ai-agentsVotes: 0GitHub stars: 191