20 skills published by Mark393295827 across 1 repository. Together they weigh 46 633 tokens — that is what loading all of them at once would cost you in context.
20 skills 46 633 tokens total
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command.
Use when property-service operations need an AI plus ontology plus DMAIC design for work orders, dispatch, quotes, evidence, CTQ metrics, and control dashboards.
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.
Use when a goal must be converted into a repeatable behavior, cue, SOP, review cadence, and identity-aligned reinforcement.
Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
Use when a long-running agent task needs context budgeting, checkpointing, compaction, retrieval, or capability-based model routing.
Use when a defined problem needs diverse ideas, cross-domain combinations, and cheap experiments instead of a single untested answer.
Use when planning or closing a daily knowledge-compounding cycle across input, cognition, wiki, behavior, creativity, output, and feedback.
Use when a decision-relevant question needs multi-source search, claim-level citations, contradiction handling, uncertainty, or a durable wiki handoff.
Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
Use when a completed work session should yield durable concepts, corrections, decisions, reusable patterns, and a traceable next action.
Use when a startup needs an evidence-weighted health check, investor lens, runway diagnosis, top constraint, or cheapest next validation test.
Use when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.
Use when a PDF, URL, transcript, clipping, or raw note must become source-grounded, linked, governed knowledge in an Obsidian vault.
Use when an Obsidian wiki needs a reproducible health audit for structure, provenance, links, understanding, lifecycle, and promotion readiness.