selamy-labs
- 110 skills
- 0 followers
- 6 hours ago last updated
- ▌ Process Aware Done · selamy-labsUse when reporting or reviewing done, verified, passed, sent, matched, green, or complete claims. Requires artifact evidence plus a legitimate, reproducible path to the result.
- ▌ Protobuf Authoring · selamy-labsUse 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.
- ▌ Regression Ratchet · selamy-labsUse 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.
- ▌ Restart Resilience · selamy-labsUse 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.
- ▌ Table Driven Tests · selamy-labsUse when one behavior should be checked against many input and output cases. Put cases in a named table and run the same assertion path.
- ▌ Trajectory Scoring · selamy-labsUse 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.
- ▌ Adaptive Estimation · selamy-labsUse 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.
- ▌ Agentic Coding Loop · selamy-labsUse 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.
- ▌ Codegraph Bootstrap · selamy-labsUse 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.
- ▌ Connector Readiness · selamy-labsUse 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.
- ▌ Full Disk Forensics · selamy-labsUse 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.
- ▌ Grounded Generation · selamy-labsUse when generating content, reports, summaries, evaluations, or code against external facts. Requires verified source data, explicit lineage, and no invented capabilities or copied answers.
- ▌ Parse Dont Validate · selamy-labsUse 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.
- ▌ Technical Integrity · selamy-labsUse 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.
- ▌ Authoring HTML Email · selamy-labsBuild client-facing HTML email that actually renders — correct multipart MIME (HTML + plain-text fallback ALWAYS), inline styles, and verify by rendering the received message.
- ▌
- ▌ Verify Real Artifact · selamy-labsUse 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.
- ▌ Agent Otel Trajectory · selamy-labsEmit 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.
- ▌ Agents As Iac Modules · selamy-labsUse 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.
- ▌ Challenge The Premise · selamy-labsUse 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.
- ▌ Enums Codify Behavior · selamy-labsUse when behavior modes are represented by booleans, strings, or repeated conditionals. Prefer enums or tagged unions with behavior per case.
- ▌ Github Pr Shepherding · selamy-labs bundleUse when monitoring, unblocking, or driving GitHub pull requests through required checks, auto-merge, merge queues, runner pickup, or blocker comments. Classify PR state from GitHub as the system of record, verify auth context, preserve CI capacity, checkpoint waits, and report merged or blocked with evidence.
- ▌ Iac Incident Response · selamy-labsUse during infrastructure outages when fixes must preserve declarative source of truth instead of leaving live manual drift behind.
- ▌ Lean On Oss Standards · selamy-labsUse when choosing implementation patterns for observability, runtime configuration, API typing, CI, auth, or infrastructure. Biases toward proven open standards before custom machinery.
- ▌ Live Money Discipline · selamy-labsUse 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.
- ▌ Product Feedback Loop · selamy-labsUse 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.
- ▌ Single Responsibility · selamy-labsUse 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.
- ▌
- ▌ Verify Delegated Work · selamy-labsUse 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.
- ▌ Early Return Over Else · selamy-labsUse when control flow is getting nested or hard to scan. Prefer guard clauses and early returns while preserving behavior with tests.
- ▌ Polyglot Monorepo Arch · selamy-labsUse 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.
- ▌ Property Based Testing · selamy-labsUse 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.
- ▌ Resilient Pool Refresh · selamy-labsUse 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.
- ▌
- ▌ Rwo Volume Maintenance · selamy-labsUse 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.
- ▌ Steelman Then Critique · selamy-labsUse 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.
- ▌ Adaptive Loop Budgeting · selamy-labsUse 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.
- ▌
- ▌ Batched Ssh Enumeration · selamy-labsUse 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.
- ▌ Data Connector Building · selamy-labsUse when building integrations or replacing synthetic demos with real data sources. Requires source contracts, idempotent ingestion, validation, observability, and fixture-backed tests.
- ▌ Disk Pressure Forensics · selamy-labsUse when disk usage is high, df and du disagree, or an agent must diagnose full filesystems without deleting valuable work.
- ▌ Live State Verification · selamy-labsUse when verifying service health, deployed state, cluster objects, credentials, or automation results where the wrong auth context can produce false empty results.
- ▌ Prefer Fakes Over Mocks · selamy-labsUse 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.
- ▌ Stacked Diff Discipline · selamy-labsUse when dependent multi-step changes tempt one big PR or a pile of conflicting branches. Stack small dependency-ordered PRs, keep stacks short, and draft the upper members so N stacked PRs don't multiply CI cost.
- ▌ Terraform Module Layout · selamy-labsUse when creating, reviewing, or restructuring Terraform or OpenTofu modules. Enforces a canonical file layout and cohesion-based module boundaries.
- ▌ Typed Rewrite Migration · selamy-labsUse 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.
- ▌ Malicious Skill · selamy-labsA poisoned skill used only as a negative fixture for the security gate.
- ▌ Oke Arc Runners Opentofu · selamy-labsUse 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.
- ▌ Public Repo CI Isolation · selamy-labsUse 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.
- ▌ Tooling First Automation · selamy-labsUse 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.
- ▌
- ▌ Colocated Pod Tolerations · selamy-labsUse 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.
- ▌ Context Anchored Patching · selamy-labsUse 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.
- ▌ Evidence Claim Boundaries · selamy-labsUse when verifier output, schemas, fixtures, templates, CI, or readiness artifacts are being used to support live, human-gated, hardware, deployment, or completion claims.
- ▌ Merge Conflict Discipline · selamy-labsResolve merge conflicts by intent (never blind accept-ours/theirs) AND prevent them structurally — integrate, never clobber.
- ▌ Verified Secret Migration · selamy-labsUse when moving a credential or secret into a secret manager without leaking it or destroying the source before byte-accurate readback verification.
- ▌ Codegraph Worktree Startup · selamy-labsUse 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.
- ▌ Safe Remote Shell Commands · selamy-labs bundleUse 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.
- ▌ Self Improving Agent Loops · selamy-labsUse 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.
- ▌ Continuous Issue Resolution · selamy-labsUse when an agent should treat GitHub issues as an ongoing work queue, including triage, decomposition of oversized issues into smaller child issues, PR-based implementation, verification, and evidence-backed issue closure.
- ▌ Interface Over Conditionals · selamy-labsModel 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.
- ▌
- ▌
- ▌ Criticality Tiered Reporting · selamy-labsUse 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.
- ▌
- ▌ Low Level Executor Task Spec · selamy-labsUse 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.
- ▌ Self Hosted Runner Substrate · selamy-labsUse when designing or repairing Kubernetes-backed self-hosted CI runners, especially Actions Runner Controller, runner scale sets, registry pulls, autoscaling, failover, or reproducible infrastructure.
- ▌ Verify From System Of Record · selamy-labsAbsence of visibility is not absence of the thing — verify state, identity, and existence against the system of record, not a partial or cached view.
- ▌ Ephemeral Workspace Lifecycle · selamy-labs bundleUse 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.
- ▌ Instrumented Service Scaffold · selamy-labsUse when creating or reviewing a new long-running service so observability, runtime flags, tests, coverage gates, and release controls exist from the first commit.
- ▌ Oversized Description · selamy-labsThis is a very long description that contains way too many words and should be rejected by the validator because it exceeds the forty five word limit that is enforced by the naming lint checker which ensures skill descriptions stay concise and readable for humans and machines alike without unnecessary verbosity or padding
- ▌ Map Dispatch Over Conditionals · selamy-labsUse when stable named cases are implemented as long if or switch chains. Prefer table, map, or strategy dispatch with explicit fallback behavior.
- ▌ Stakeholder Knowledge Projection · selamy-labs bundleUse 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.
- ▌ Graceful Shutdown Stateful Agents · selamy-labsMake a stateful container/agent survive SIGTERM→SIGKILL on Kubernetes without losing in-flight work or corrupting on-disk state.
- ▌ Secret To Secret Manager Verified · selamy-labsUse 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.
- ▌ Feature Coverage Not Just Line Coverage · selamy-labsUse when coverage percentage is treated as proof. Require named feature behavior tests, source fixtures, and anti-overfit checks alongside line coverage.
- ▌ Structure Improves Agent Predictability · selamy-labsUse 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.
- ▌ Skill Judge · selamy-labsUse 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.
- ▌
- ▌ Using Laneq · selamy-labsUse when draining a laneq priority queue. Covers the pull loop, priority semantics, well-formed directives, and queue hygiene.
- ▌ Email Triage · selamy-labsUse 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.
- ▌ Sim Zero Mode · selamy-labsUse 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.
- ▌ Wiki Building · selamy-labsUse 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.
- ▌ Yield On Wait · selamy-labsUse 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.
- ▌ Event Sourcing · selamy-labsUse 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.
- ▌ Iac Not Ad Hoc · selamy-labsUse for infrastructure, repository settings, cloud resources, Kubernetes, runner, secret, cron, runtime config, or deployment changes. Requires a declarative source of truth.
- ▌ Skill Curation · selamy-labsUse 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.
- ▌ Agent Drives UI · selamy-labsUse 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.
- ▌ C4 Architecture · selamy-labsUse 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.
- ▌ Command Creator · selamy-labsUse 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.
- ▌ Orchestrate Agy · selamy-labs bundleReliably 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.
- ▌ Reddit Research · selamy-labsUse when collecting Reddit discussion signals for research, trend discovery, or hypothesis generation. Requires terms-aware access, source lineage, rate-limit discipline, and clear uncertainty.
- ▌ Adopt And Delete · selamy-labsUse 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.
- ▌ Ascii UI Mockups · selamy-labsUse 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.
- ▌ Credential Proxy · selamy-labsUse 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.
- ▌ Exhaustive Match · selamy-labsUse when every known variant must be handled. Prefer compiler, type-checker, linter, or test-enforced exhaustive matches.
- ▌ Gate Before Push · selamy-labsUse 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.
- ▌ Mermaid Diagrams · selamy-labsUse 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.
- ▌ Parameter Design · selamy-labsUse 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.
- ▌ Plugin Authoring · selamy-labsUse 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.