Mikal
Community@mikalv · Oslo, Norway
Working as security architect and programmer. Language agnostic, security focused.
Agent Skills by Mikal
Showing 72 vetted skills indexed across 1 GitHub repositories.
context-management
Manages conversation context with checkpoints, timeline review, and compaction at phase boundaries.
self-healing
Runs a bounded two-cycle review-and-repair loop using stress-interview and worker subagents.
stress-interview
Runs verifier, reviewer, and challenger subagents in parallel to pressure-test changes before release.
mcp-scripting
Write JavaScript to discover, inspect, and orchestrate MCP tool calls.
telegram-bot
Look up Telegram Bot API methods, types, and update shapes in a local reference.
domain-dag
Validates acyclic local import graphs and domain ownership boundaries in modular codebases.
telegram-bridge
Operates Telegram turns, replies, attachments, buttons, voice, and Threaded Mode routing for Pi sessions.
generated-control-surface
Generates contextual prompt-button control surfaces for Telegram from current state and user intent.
research
Investigate questions against primary sources and save cited findings as Markdown files.
domain-modeling
Build and maintain a project domain glossary and architectural decision records.
wayfinder
Plans large efforts as decision tickets on an issue tracker and resolves them one per session.
setup-matt-pocock-skills
Configure a repository's issue tracker, triage labels, and domain doc layout for engineering skills.
writing-great-skills
Provides vocabulary and principles for writing predictable agent skills.
handoff
Generates a handoff document summarizing the current conversation for a fresh agent session.
diagnosing-bugs
Diagnose hard bugs and performance regressions through a structured six-phase feedback-loop workflow.
code-review
Reviews git diffs against coding standards and the originating spec using parallel sub-agents.
to-tickets
Breaks plans and specs into tracer-bullet tickets with declared blocking dependencies.
ask-matt
Routes user situations to the appropriate skill or workflow in the repository.
improve-codebase-architecture
Scan a codebase for module deepening opportunities and render them as a visual HTML report.
to-spec
Synthesizes conversation context into a structured spec and publishes it to the project issue tracker.
codebase-design
Designs deep modules with small interfaces placed at clean, testable seams.
triage
Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.
prototype
Build throwaway logic or UI prototypes to answer design questions.
resolving-merge-conflicts
Resolves in-progress git merge and rebase conflicts while preserving both change intents.
Frequently Asked Questions About Mikal
FAQPage SchemaWhat tasks can I accomplish with Mikal's skill collection?▼
You can diagnose bugs, run test-driven development, review PRs against standards and specs, resolve merge conflicts, manage git worktrees, build Elixir/Phoenix and Iced GUI applications, operate Telegram bots, conduct deep research, and execute plan-first development from grilled specs through phased implementation.
Who is the target audience for these skills?▼
Software engineers, security architects, and technical leads working in agent-assisted coding environments. The skills suit developers maintaining modular codebases, running disciplined review cycles, managing Linear or GitHub issue trackers, and building Elixir, Phoenix LiveView, or Rust Iced applications.
How do the planning and orchestration skills work in practice?▼
Start with grill or scout to stress-test the idea, synthesize a spec via to-spec, break it into blocking tickets with to-tickets, then implement phase by phase. The orch skill handles single work items end to end: prepare, delegate, review, submit, merge, and handoff.
Are these skills open source and what do they cost?▼
Many skills carry an explicit MIT license, including reviewer, linear, worktree, decider, iced-rs, and project-management, sourced from the vanillagreen/vstack repository. They are free to use; other skills in the manifest declare no license and should be treated as unlicensed.
What prerequisites or dependencies do these skills require?▼
Dependencies vary per skill: orch requires github, worktree, dev, project-management, and decider; project-management requires Linear and GitHub access; dep-radar requires GitHub; iced-shadcn requires iced-rs. Several skills are standalone with no declared dependencies.