Almog Baku
Community@almogbaku · Israel
LLM hacker
Agent Skills by Almog Baku
Showing 27 vetted skills indexed across 2 GitHub repositories.
AlmogBakuprefix-cap
Serves as the entry skill for validating prefix-format conventions.
AlmogBakuprefix-cap-tidy
Scopes role-based tidying work to the main agent within a capability fixture.
AlmogBakubad-cap-sorted
Provides a lint fixture skill whose identifier already carries its prefix.
AlmogBakucapture
Hands off execution to the refer skill and then the capture skill.
AlmogBakurefer
Owns a nested reference fixture for testing nested-reference and reference-toc lint checks.
AlmogBakuclaude-helper
Provides a minimal fixture skill for testing reserved-word validation in lint tooling.
AlmogBakuname-cap
Serves as the entry skill for the name fixture capability installation flow.
AlmogBakughost
Provides an undeclared skill fixture for testing manifest validation checks.
AlmogBakuinit
Creates and scaffolds a new git-based knowledge base with zones, grants, and maintenance schedules.
AlmogBakuroute
Routes content to the correct knowledge base using tags, rules, and model classification.
AlmogBakukb
Explains knowledge base layout, queue semantics, expiry, links, and maintenance for git-backed markdown bases.
AlmogBakuadopt
Registers an existing knowledge tree as a base and reports divergence without writing into it.
AlmogBakurecall
Answers questions from stored knowledge bases with cited sources and explicit gap reporting.
AlmogBakuimport
Migrates external knowledge bases into a target base through interactive checkpointed batches.
AlmogBakuschedule
Estimates commitments and blocks calendar time for them within working hours.
AlmogBakuupdate
Updates existing commitments in a knowledge base when users report progress, stalls, or abandonment.
AlmogBakusteward
Maintains a commitments backlog by detecting overdue, stalled, and expired items via kb queries.
AlmogBakuwork-tracker
Answers questions about personal commitments by querying a knowledge base of tracked actions.
AlmogBakuupgrade
Re-applies user MOD.md deltas onto fresh upstream capability renders with diff-gated commits.
AlmogBakuremove
Removes installed aos capabilities by walking lockfile entries backwards through jobs, symlinks, and config keys.
AlmogBakuinstall
Installs aos capabilities into an agent harness with name gating, rendering, and diff-gated materialization.
AlmogBakuevolve
Records per-user adjustments to installed aos capabilities in MOD.md so they survive upgrades.
AlmogBakuonboard
Runs capability onboarding interviews and writes typed answers to MOD.md overlay files.
AlmogBakucontribute
Drafts and applies source-level changes to shared capability packages with scoped contribution workflows.
Frequently Asked Questions About Almog Baku
FAQPage SchemaWhat tasks can I perform with AlmogBaku's aos skills?▼
You can manage the full capability lifecycle (install, onboard, upgrade, evolve, remove, contribute, review, build), run personal knowledge bases (init, adopt, import, capture, route, recall), and track commitments (capture, schedule, update, steward). An existing skill also enables interactive source debugging via Debug Adapter Protocol.
Who are these skills designed for?▼
They target individual users running an aos harness who want persistent, personalized capabilities: people maintaining knowledge bases or Obsidian vaults, tracking their own commitments and calendar time, and contributors packaging or reviewing capabilities for upstream distribution.
How does capability installation and personalization work?▼
capability-install reads the capability briefing, gates claimed skill names, runs the onboarding interview, and renders agents, symlinks, schedules and context blocks behind a diff gate. Personal answers and tweaks live in the user's MOD.md overlay, which capability-upgrade re-applies to fresh upstream so personalization survives every update.
How do the knowledge base skills handle my existing notes?▼
kb-adopt registers an existing tree or Obsidian vault in place without writing to it, optionally running kb migrate for old layouts. kb-import bulk-imports another base's content interactively in checkpointed batches, leaving the source byte-intact. kb-init scaffolds a fresh base with zones, types and maintenance schedules.
What prerequisites do these skills assume?▼
Skills assume an installed aos harness with a manifest and lockfile, since lifecycle skills walk lockfile entries and gate skill-name claims. Knowledge base skills expect a base tree on disk or one to scaffold; work-tracker skills expect a commitments base and access to the user's calendar for time blocking.