all publishers

selamy-labs

@selamy-labs source repo

109 published skills · page 1 of 2

  1. ▌
    Process Aware Done · selamy-labs
    Use when reporting or reviewing done, verified, passed, sent, matched, green, or complete claims. Requires artifact evidence plus a legitimate, reproducible path to the result.
    0 repo stars
  2. ▌
    Agentic Coding Loop · selamy-labs
    Use when implementing code from a spec through a bounded build-test-fix loop with explicit acceptance criteria, automated checks, live verification when needed, and clear stop conditions.
    0 repo stars
  3. ▌
    Authoring HTML Email · selamy-labs
    Build client-facing HTML email that actually renders — correct multipart MIME (HTML + plain-text fallback ALWAYS), inline styles, and verify by rendering the received message.
    0 repo stars
  4. ▌
    Github Pr Shepherding · selamy-labs bundle
    Use when monitoring, unblocking, or driving GitHub PRs or native stacks through required checks, group merge, merge queues, auto-merge for ordinary PRs, runner pickup, or blocker comments. Verify current GitHub state and report merged or blocked with evidence.
    0 repo stars
  5. ▌
    Small Focused Changes · selamy-labs
    Small, Focused Changes
    0 repo stars
  6. ▌
    Verify Delegated Work · selamy-labs
    Use when accepting, merging, or building on work produced by a sub-agent, delegated worker, or any process you did not run yourself. A worker's done, idle, or green-CI signal is a claim, not proof — independently verify the real artifact first.
    0 repo stars
  7. ▌
    Property Based Testing · selamy-labs
    Use when example tests can't cover the input space — parsers, serializers, encoders, money math, state machines, anything with a roundtrip or invariant. Assert properties that hold for all inputs, let the framework generate cases and shrink failures to a minimal counterexample.
    0 repo stars
  8. ▌
    Stacked Diff Discipline · selamy-labs bundle
    Use when splitting dependent work into reviewable PRs, continuing above an unmerged prerequisite, converting existing branches into a stack, or merging a GitHub stack together. Also use when serial PR admission or repeated rebases delay dependent work.
    0 repo stars
  9. ▌
    Terraform Module Layout · selamy-labs
    Use when creating, reviewing, or restructuring Terraform or OpenTofu modules. Enforces Google-recommended module file layout and cohesion-based module boundaries.
    0 repo stars
  10. ▌
    Evidence Claim Boundaries · selamy-labs
    Use when verifier output, schemas, fixtures, templates, CI, or readiness artifacts are being used to support live, human-gated, hardware, deployment, or completion claims.
    0 repo stars
  11. ▌
    Continuous Issue Resolution · selamy-labs
    Use when an agent should continuously resolve an authorized backlog through bounded implementation, tested PRs, independent review, and evidence-backed closure. GitHub Issues may hold the queue; an existing authoritative backlog works too.
    0 repo stars
  12. ▌
    Low Level Executor Task Spec · selamy-labs
    Use when dispatching a task to an autonomous executor or sub-agent that does not share your context. Spell out exact paths, the literal access command, naming and identity conventions, and known gotchas — assume zero tribal knowledge.
    0 repo stars
  13. ▌
    Test Design · selamy-labs
    Test Design
    0 repo stars
  14. ▌
    Using Laneq · selamy-labs
    Use when draining a laneq priority queue. Covers the pull loop, priority semantics, well-formed directives, and queue hygiene.
    0 repo stars
  15. ▌
    Yield On Wait · selamy-labs
    Use when CI, deploys, image builds, infrastructure applies, certificates, queues, or other long-running waits would otherwise stall an agent. Requires a durable checkpoint before switching work.
    0 repo stars
  16. ▌
    Gate Before Push · selamy-labs
    Use before opening a pull request. Reproduce the repository's OWN CI gates locally and make them green first — including its bespoke checks — so the PR arrives green and merges first-try instead of burning scarce CI iterations.
    0 repo stars
  17. ▌
    Orchestrate Claude · selamy-labs bundle
    Reliably launch, supervise, resume, and hand off Claude Code as an interactive tmux worker. Use for bounded Claude delegation, remote or alternate-user operation, auth recovery, dedicated quota routing, and proving a directive was submitted rather than merely pasted.
    0 repo stars
  18. ▌
    Portfolio Delivery Control · selamy-labs bundle
    Check a multi-project delivery ledger deterministically at coordinator wakeups, directive intake, worker admission, review readiness, and witness follow-through. Use when projects disappear, ready work ages, evidence conflicts, or parallel work becomes serial. Composes maintained transport and review mechanisms without adding supervisors.
    0 repo stars
  19. ▌
    Radical Brevity · selamy-labs bundle
    Use as a final edit for prose on any communication surface, including email, chat, documents, commit and PR descriptions, review comments, and prose in diffs. Cut words while preserving meaning, context, accuracy, tone, and action.
    0 repo stars
  20. ▌
    Pull Request Writing · selamy-labs
    Use when opening or updating a pull request title and description so a reviewer who has not read the agent conversation can understand and verify the change.
    0 repo stars
  21. ▌
    Protobuf Authoring · selamy-labs
    Use when writing or reviewing a .proto schema. Apply consistent naming/style and — the part that actually bites — the wire- and consumer-compatibility rules, so the schema reads cleanly and can evolve without breaking deployed readers. Gate it with buf lint plus breaking-change detection.
    0 repo stars
  22. ▌
    Regression Ratchet · selamy-labs
    Use when fixing a bug, incident, or regression. In the same change, add the guard that would have caught it — matched to the failure class — so the problem can recur at most once. A fix without its ratchet is half-done.
    0 repo stars
  23. ▌
    Restart Resilience · selamy-labs
    Use when a stateful worker or service can be restarted, rescheduled, or crash mid-task. Guarantees it resumes its full in-flight and scheduled work from durable state on any restart, never silently dropping work.
    0 repo stars
  24. ▌
    Table Driven Tests · selamy-labs
    Use when one behavior should be checked against many input and output cases. Put cases in a named table and run the same assertion path.
    0 repo stars
  25. ▌
    Trajectory Scoring · selamy-labs
    Use when evaluating an agent run, reviewing fleet performance, designing trajectory telemetry, or grading the journey rather than only the final answer. Applies promise-and-progress scoring to each step without requiring a trained reward model.
    0 repo stars
  26. ▌
    Adaptive Estimation · selamy-labs
    Use when tracking a slowly-varying latent quantity from noisy measurements with quantifiable uncertainty — a drifting metric, capacity, latency trend, or confidence. Prefer a Kalman-style adaptive estimator over fixed moving averages or static thresholds.
    0 repo stars
  27. ▌
    Codegraph Bootstrap · selamy-labs
    Use when starting code exploration or implementation in a repository where CodeGraph may be available. Ensure CodeGraph is installed/initialized when authorized, then prefer CodeGraph queries for semantic code context.
    0 repo stars
  28. ▌
    Connector Readiness · selamy-labs
    Use when installing, repairing, or verifying an MCP or other authenticated connector, especially when configuration, authentication, quota, and real artifact access can be mistaken for one another.
    0 repo stars
  29. ▌
    Full Disk Forensics · selamy-labs
    Use when a filesystem is full or nearly full, especially when df and du disagree. Checks deleted-open files, privilege blind spots, journald, temp worktrees, caches, and safe cleanup evidence.
    0 repo stars
  30. ▌
    Grounded Generation · selamy-labs
    Use when generating content, reports, summaries, evaluations, or code against external facts. Requires verified source data, explicit lineage, and no invented capabilities or copied answers.
    0 repo stars
  31. ▌
    Parse Dont Validate · selamy-labs
    Use at a boundary that takes untrusted input — API, config, user data, a queue message. Parse it into a typed value that makes invalid states unrepresentable, instead of validating and passing the raw data onward for the core to re-check or blindly trust.
    0 repo stars
  32. ▌
    Technical Integrity · selamy-labs
    Use on EVERY operator/principal request and on your own ideas — make the soundest engineering/judgment call and disagree with evidence when warranted; never appease, never manufacture disagreement. The bar is TRUTH, not agreement.
    0 repo stars
  33. ▌
    Product Loss Descent · selamy-labs
    Product Loss Descent (PLD)
    0 repo stars
  34. ▌
    Verify Real Artifact · selamy-labs
    Use when validating whether a send, deploy, workflow, document, trace, or product flow really landed or works. Focuses verification on the real artifact instead of logs or indirect proxies.
    0 repo stars
  35. ▌
    Agent Otel Trajectory · selamy-labs
    Emit OpenTelemetry trajectory spans (tool-call, latency, token usage) as an agent works — vendor-neutral, via otel-cli wrapping shell tool-calls, exported to any OTLP backend.
    0 repo stars
  36. ▌
    Agents As Iac Modules · selamy-labs
    Use when onboarding, scaling, decommissioning, or auditing autonomous agents (or any "software employee") in a fleet. Model each agent as a reusable infrastructure-as-code module whose inputs are its facets, so its whole configuration is declarative, reviewable, and reproducible.
    0 repo stars
  37. ▌
    Challenge The Premise · selamy-labs
    Use when a request bakes in an assumption that may be wrong — a leading question, an already-chosen approach, a framing. Interrogate the premise before answering as asked; if the question itself is flawed, say so and answer the better question, with reasoning.
    0 repo stars
  38. ▌
    Enums Codify Behavior · selamy-labs
    Use when behavior modes are represented by booleans, strings, or repeated conditionals. Prefer enums or tagged unions with behavior per case.
    0 repo stars
  39. ▌
    Iac Incident Response · selamy-labs
    Use during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.
    0 repo stars
  40. ▌
    Lean On Oss Standards · selamy-labs
    Use when choosing implementation patterns for observability, runtime configuration, API typing, CI, auth, or infrastructure. Biases toward proven open standards before custom machinery.
    0 repo stars
  41. ▌
    Live Money Discipline · selamy-labs
    Use when building or changing a system whose actions are irreversible — moving money, trading, production deploys, data deletion, external sends. Gate every live action behind dry-run, explicit go-live signoff, a kill switch, and blast-radius limits, and default to the reversible path.
    0 repo stars
  42. ▌
    Product Feedback Loop · selamy-labs
    Use when turning stakeholder, reviewer, customer, beta, analytics, or interview feedback into product decisions, tracked work, evals, experiments, or an explicit decision to gather more evidence.
    0 repo stars
  43. ▌
    Single Responsibility · selamy-labs
    Use when a class, function, module, or file is hard to reason about. A unit you cannot describe in one sentence holds too many responsibilities; decompose it into single-responsibility units that collaborate through clear interfaces.
    0 repo stars
  44. ▌
    Early Return Over Else · selamy-labs
    Use when control flow is getting nested or hard to scan. Prefer guard clauses and early returns while preserving behavior with tests.
    0 repo stars
  45. ▌
    Polyglot Monorepo Arch · selamy-labs
    Use when choosing build and packaging tooling for a multi-language monorepo. Earn complexity before adopting it — a shared schema contract plus each language's native tooling beats Bazel, Nix, or rules_oci until reproducibility or scale pain is concrete and fleet-wide.
    0 repo stars
  46. ▌
    Resilient Pool Refresh · selamy-labs
    Use when a job refreshes or validates a pool of credentials, tokens, sessions, or connections. Isolate per-item failures, classify terminal (needs human re-auth) versus transient (auto-retry), and alert clearly instead of failing the whole batch silently.
    0 repo stars
  47. ▌
    REST Resource Modeling · selamy-labs
    REST Resource Modeling
    0 repo stars
  48. ▌
    Rwo Volume Maintenance · selamy-labs
    Use when a job does maintenance on a single-writer (ReadWriteOnce) volume or live database that a running service still owns — pruning, compaction, retention, vacuum. Prefer snapshot/offline processing and bound the job generously so it cannot starve itself.
    0 repo stars
  49. ▌
    Steelman Then Critique · selamy-labs
    Use when critiquing a proposal, design, or argument. First state its strongest form — the best honest case for it — then critique that, so the critique actually lands instead of knocking down a weak version or rubber-stamping a flawed one.
    0 repo stars
  50. ▌
    Adaptive Loop Budgeting · selamy-labs
    Use when an autonomous loop needs explicit limits on attempts, time, cost, tool calls, verification depth, or risk, and a clear stop, continue, yield, or escalate decision.
    0 repo stars
  51. ▌
    Authoring Skills Vs MCP · selamy-labs
    Authoring: Skills vs MCP Servers
    0 repo stars
  52. ▌
    Batched Ssh Enumeration · selamy-labs
    Use when a loop or watchdog SSHes across many hosts to probe, enumerate, or act. Force non-interactive SSH with timeouts so one un-authable host cannot hang the loop, and check a heartbeat so a stuck-but-alive process is detected.
    0 repo stars
  53. ▌
    Data Connector Building · selamy-labs
    Use when building integrations or replacing synthetic demos with real data sources. Requires source contracts, idempotent ingestion, validation, observability, and fixture-backed tests.
    0 repo stars
  54. ▌
    Disk Pressure Forensics · selamy-labs
    Use when disk usage is high, df and du disagree, or an agent must diagnose full filesystems without deleting valuable work.
    0 repo stars
  55. ▌
    Live State Verification · selamy-labs
    Use when verifying service health, deployed state, cluster objects, credentials, or automation results where the wrong auth context can produce false empty results.
    0 repo stars
  56. ▌
    Prefer Fakes Over Mocks · selamy-labs
    Use when choosing or reviewing test doubles — deciding between a fake, stub, or mock for a collaborator. Default to fakes (working in-memory implementations); reserve interaction mocks for the narrow cases where the interaction itself is the contract.
    0 repo stars
  57. ▌
    Typed Rewrite Migration · selamy-labs
    Use when migrating an untyped or legacy core to a typed/rewritten one without a risky big-bang cutover. Strangle it incrementally behind a stable boundary, run old and new in parallel to prove equivalence, and cut over slice by slice while both stay green.
    0 repo stars
  58. ▌
    Oke Arc Runners Opentofu · selamy-labs
    Use when designing, reviewing, or implementing self-hosted GitHub Actions runners on Oracle Kubernetes Engine with Actions Runner Controller and OpenTofu. Covers runner scale sets, GitHub App secrets, OKE kubeconfig, autoscaling, and declarative rollout boundaries.
    0 repo stars
  59. ▌
    Public Repo CI Isolation · selamy-labs
    Use when configuring CI for a public or fork-accepting repository, or choosing runners for untrusted pull requests. Untrusted fork code must never run on a trusted self-hosted runner with access to secrets or internal network.
    0 repo stars
  60. ▌
    Tooling First Automation · selamy-labs
    Use when a task can be performed through existing callable tooling, MCP servers, browser automation, CLI wrappers, or service APIs before writing bespoke scripts or ad hoc automation. Especially relevant for browser/UI automation, external-system actions, and repeated operational workflows.
    0 repo stars
  61. ▌
    Colocated Pod Tolerations · selamy-labs
    Use when a Kubernetes Job, CronJob, or Pod is pinned to a specific node (via podAffinity, nodeSelector, or nodeAffinity) to share a node or an RWO volume. It must also carry that node's tolerations or it is permanently unschedulable.
    0 repo stars
  62. ▌
    Context Anchored Patching · selamy-labs
    Use when patching code you do not fully control or that moves between runs. Anchor edits on unique surrounding context and verify by behavior, never by line number or a grep that only confirms the text is present somewhere.
    0 repo stars
  63. ▌
    Merge Conflict Discipline · selamy-labs
    Resolve merge conflicts by intent (never blind accept-ours/theirs) AND prevent them structurally — integrate, never clobber.
    0 repo stars
  64. ▌
    Verified Secret Migration · selamy-labs
    Use when moving a credential or secret into a secret manager without leaking it or destroying the source before byte-accurate readback verification.
    0 repo stars
  65. ▌
    Codegraph Worktree Startup · selamy-labs
    Use when starting or resuming code work in a repository. Verify CodeGraph, initialize or sync the local graph, keep indexes uncommitted, and prefer graph queries before broad file reads.
    0 repo stars
  66. ▌
    Safe Remote Shell Commands · selamy-labs bundle
    Use when commands cross shell boundaries through SSH, nested shells, tmux, heredocs, substitutions, variables, or quoted data. Prevent expansion by the wrong interpreter, simplify transport, and verify resulting state.
    0 repo stars
  67. ▌
    Self Improving Agent Loops · selamy-labs
    Use when designing a system that should autonomously generate, evaluate, and refine its own candidate solutions (agents, prompts, configurations, experiments) in a loop — rather than hand-managing each iteration. The system does the search; the human owns the architecture and the final decision.
    0 repo stars
  68. ▌
    Interface Over Conditionals · selamy-labs
    Model behavioral variation as an interface with N implementations and select the right one for the context — instead of branching on a type/flag at every call site.
    0 repo stars
  69. ▌
    Source History Decision Log · selamy-labs
    Source-History Decision Log
    0 repo stars
  70. ▌
    Criticality Tiered Reporting · selamy-labs
    Use when deciding what a service or worker should report and how loudly — alerts, progress updates, logs, notifications. Tier output by criticality so the important signal is not buried in routine chatter.
    0 repo stars
  71. ▌
    Loop Governance And Learning · selamy-labs
    Loop Governance And Learning
    0 repo stars
  72. ▌
    Self Hosted Runner Substrate · selamy-labs
    Use when designing or repairing Kubernetes-backed self-hosted CI runners, especially Actions Runner Controller, runner scale sets, registry pulls, autoscaling, failover, or reproducible infrastructure.
    0 repo stars
  73. ▌
    Verify From System Of Record · selamy-labs
    Absence of visibility is not absence of the thing — verify state, identity, and existence against the system of record, not a partial or cached view.
    0 repo stars
  74. ▌
    Ephemeral Workspace Lifecycle · selamy-labs bundle
    Use when creating, inheriting, handing off, or cleaning a temporary worktree, clone, task directory, build output, or local cache. Give every ephemeral resource an owner and terminal cleanup contract, preserve dirty work, and prevent scratch storage from exhausting its host.
    0 repo stars
  75. ▌
    Instrumented Service Scaffold · selamy-labs
    Use when creating or reviewing a new long-running service so observability, runtime flags, tests, coverage gates, and release controls exist from the first commit.
    0 repo stars
  76. ▌
    Map Dispatch Over Conditionals · selamy-labs
    Use when stable named cases are implemented as long if or switch chains. Prefer table, map, or strategy dispatch with explicit fallback behavior.
    0 repo stars
  77. ▌
    Stakeholder Knowledge Projection · selamy-labs bundle
    Use when translating authoritative project knowledge into stakeholder-facing Google Docs, Sheets, dashboards, journey evidence, or human task lists. Preserves source authority, audience-specific detail, native collaboration structures, protected manual decisions, assignment consent, freshness, and sync auditability.
    0 repo stars
  78. ▌
    Graceful Shutdown Stateful Agents · selamy-labs
    Make a stateful container/agent survive SIGTERM→SIGKILL on Kubernetes without losing in-flight work or corrupting on-disk state.
    0 repo stars
  79. ▌
    Secret To Secret Manager Verified · selamy-labs
    Use when migrating a secret from any source into a secret manager. Requires non-empty extraction, exact-byte preservation, readback hash verification, and source destruction only after verified match.
    0 repo stars
  80. ▌
    Feature Coverage Not Just Line Coverage · selamy-labs
    Use when coverage percentage is treated as proof. Require named feature behavior tests, source fixtures, and anti-overfit checks alongside line coverage.
    0 repo stars
  81. ▌
    Structure Improves Agent Predictability · selamy-labs
    Use when writing code an AI agent will later read and edit. Structure it so the next edit is obvious — typed boundaries, exhaustive matches, named dispatch, small surfaces — because well-structured code makes an agent predictable and ad-hoc code makes it guess.
    0 repo stars
  82. ▌
    Skill Judge · selamy-labs
    Use when reviewing or scoring a SKILL.md for design quality. Judge it by knowledge delta — what it teaches beyond what the model already knows — plus trigger clarity, scope, and progressive disclosure, and return specific fixes rather than a verdict.
    0 repo stars
  83. ▌
    Email Triage · selamy-labs
    Use when building or operating an agent email triage loop that turns recent inbox messages into prioritized, source-linked actions without duplicating project-specific rules across agents.
    0 repo stars
  84. ▌
    Sim Zero Mode · selamy-labs
    Use when building/testing an app or agent that depends on paid APIs or LLM calls and you must exercise plumbing/UI/harness without spend or real intelligence, for CI, demos, local dev. Activates on test without burning API budget, demo without live calls, or fakes/offline mode.
    0 repo stars
  85. ▌
    Wiki Building · selamy-labs
    Use when building or maintaining a durable LLM-compiled knowledge base from documents, transcripts, code, decisions, or other evidence. Preserves immutable sources, normative authority, claim provenance, contradiction state, staleness, and generated projections while the wiki compounds over time.
    0 repo stars
  86. ▌
    Event Sourcing · selamy-labs
    Use when designing a system where state-change history matters — audit, replay, temporal queries, debugging, or telemetry provenance. Record every change as an immutable domain event and derive state from the log; guard external side effects during replay.
    0 repo stars
  87. ▌
    Iac Not Ad Hoc · selamy-labs
    Use for infrastructure, repository settings, cloud resources, Kubernetes, runner, secret, cron, runtime config, or deployment changes. Requires a declarative source of truth.
    0 repo stars
  88. ▌
    Skill Curation · selamy-labs
    Use when deciding whether and where a skill should exist, how to scope its audience, how to avoid duplicates, and whether it belongs public or internal. This is curation (scope, place, dedup, share), not how to write one.
    0 repo stars
  89. ▌
    Agent Drives UI · selamy-labs
    Use when an agent operates a UI on the user's behalf through conversation, navigating, filling forms, updating live views, with real-time bi-directional state sync. Activates on conversational app control, agent drives the front end, agentic UX, or choosing an agent-to-app protocol.
    0 repo stars
  90. ▌
    C4 Architecture · selamy-labs
    Use when documenting a system's architecture, not just drawing one diagram. Apply the C4 model — context, container, component, deployment — choosing the level by audience, stopping at context plus container for most teams, and writing the result into versioned markdown.
    0 repo stars
  91. ▌
    Command Creator · selamy-labs
    Use when turning a repeated workflow into a Claude Code slash command. Structure the command markdown, choose argument handling and allowed tools, and write agent-executable steps so the workflow runs consistently instead of being re-explained every time.
    0 repo stars
  92. ▌
    Orchestrate Agy · selamy-labs bundle
    Reliably launch, bound, supervise, and verify lowercase `agy` in interactive tmux or headless mode. Use for AGY delegation, remote or alternate-user operation, auth recovery, quota routing, durable run evidence, and detecting silent permission or no-output failures.
    0 repo stars
  93. ▌
    Reddit Research · selamy-labs
    Use when collecting Reddit discussion signals for research, trend discovery, or hypothesis generation. Requires terms-aware access, source lineage, rate-limit discipline, and clear uncertainty.
    0 repo stars
  94. ▌
    Adopt And Delete · selamy-labs
    Use when adopting a shared module, library, chart, or service, or doing any consolidation, migration, or refactor that supersedes existing code. The change that adds the replacement must REMOVE what it replaced, in the same atomic change.
    0 repo stars
  95. ▌
    Ascii UI Mockups · selamy-labs
    Use when exploring or communicating a UI layout before writing code. Sketch the screen as a text mockup — boxes, fields, labels — and offer a few distinct variations, so the layout decision is made cheaply in a PR or chat before anyone builds it.
    0 repo stars
  96. ▌
    Credential Proxy · selamy-labs
    Use when a workload (agent, sandbox, container, CI job) must call an authenticated upstream (LLM/provider/cloud API) but should not hold the credential itself. Keep the secret in a proxy that injects it, so a compromised workload cannot exfiltrate the key.
    0 repo stars
  97. ▌
    Exhaustive Match · selamy-labs
    Use when every known variant must be handled. Prefer compiler, type-checker, linter, or test-enforced exhaustive matches.
    0 repo stars
  98. ▌
    Mermaid Diagrams · selamy-labs
    Use when you need to create, version-control, or document software as text-based diagrams — class, sequence, flowchart, ER, state, or C4. Pick the diagram type deliberately and generate Mermaid so diagrams live in the repo and stay maintainable alongside code.
    0 repo stars
  99. ▌
    Parameter Design · selamy-labs
    Use when designing or reviewing a function, method, or constructor signature. Make calls unambiguous and misuse-resistant by splitting nullable/optional control switches, removing overload ladders, and keeping defaults behavior-neutral.
    0 repo stars
  100. ▌
    Plugin Authoring · selamy-labs
    Use when packaging skills, commands, agents, or hooks into a Claude Code plugin and publishing to a marketplace. Get the directory structure, plugin.json and marketplace.json manifests, version bump, and local-test loop right so the plugin installs cleanly and is version-pinnable.
    0 repo stars