Skill UI

unslop is a powerful command-line interface (CLI) tool designed for post-processing text. It programmatically strips out common and identifiable patterns associated with AI-generated writing. Use it as a final, deterministic pass before publishing documentation, blog posts, or any content derived from large language models (LLMs), ensuring a more natural and human-like tone.

A comprehensive methodology for exploiting Time-of-Check / Time-of-Use (TOCTOU) race conditions across diverse system layers. This covers symlink swaps, file-descriptor races, kernel double-fetch vulnerabilities, and advanced window-widening primitives like FUSE slow filesystems and userfaultfd. Essential for security researchers targeting race-based privilege escalation in binaries, kernels, and container orchestrators.

This skill enforces disciplined SLO definition based on SRE principles, ensuring that reliability promises are measurable and actionable. It guides users in selecting the right SLI (Service Level Indicator), accurately calculating error budgets, setting multi-window burn-rate alerts, and reviewing existing SLO documents for common architectural flaws (e.g., targets too aggressive, wrong SLI selection). Ideal for defining, reviewing, and maintaining service reliability commitments.

This rigorous review simulates an interrogation by a Chief AI Officer (CAIO). It pressure-tests any AI plan across six critical dimensions: evaluation metrics, failure mode handling (SLOs), international regulatory compliance (e.g., EU AI Act), technical architecture (API vs. fine-tuning), cost economics, and necessary team roles. Use this when ensuring AI features are robust, safe, and commercially sound before launch or major investment.

This tool simulates a Chief Technology Officer's comprehensive review, stress-testing any major technical plan. It systematically interrogates critical areas including scaling limits (scaling cliffs), accumulated technical debt, team capacity planning, build-vs-buy economics, system reliability (SLOs), and security compliance. Use it before committing to core architecture changes or making high-stakes engineering decisions.

Provides strategic operational guidance for startup VPEs, focusing on maximizing delivery throughput using DORA metrics, optimizing the engineering hiring funnel, designing scalable team structures (squad/tribe), and establishing robust production disciplines. Use when scaling pains hit, delivery slows, or organizational design is unclear.

A dedicated skill for performing manual data synchronization and knowledge recall with OpenViking. It allows users to explicitly trigger chat transcript syncing from OpenClaw sessions and perform targeted memory searches via command line, without disrupting normal conversation flow or occupying the standard context engine slot.

A structured playbook for improving the time and space complexity (Big-O) of existing, slow code. This skill guides developers through systematic refactoring, focusing on identifying bottlenecks like nested loops or N+1 queries. It emphasizes applying transformations one at a time, maintaining test coverage, and measuring performance gains to ensure correct and efficient code.

This skill provides a direct, fast shell invocation to capture the current git diff (staged, working-tree, or specific file list) as raw text. It is designed to replace slower LLM agent steps that merely execute 'git diff' commands, significantly speeding up CI/CD workflows and meta-steps that require repository state analysis.

Drafts a complete, publication-ready research paper section (e.g., Introduction, Method, Results) as a robust LaTeX fragment. This tool ensures the section adheres strictly to a predefined writing plan, maintaining narrative coherence, managing citation budgets, and slotting seamlessly into a larger academic manuscript.

Generates a complete, structured load and performance testing plan for any service. This skill guides the definition of test objectives, establishes measurable SLO thresholds (p99, error rate, throughput), and designs multi-scenario tests (Baseline, Stress, Spike, Soak). It is essential for teams needing to set clear pass/fail criteria, select appropriate tooling (k6, Locust), and integrate performance gates into CI/CD pipelines.

This guide helps define a complete observability stack for any service. It systematically covers the Four Golden Signals (latency, traffic, errors, saturation), guiding users to define core metrics, set Service Level Objectives (SLOs), configure actionable alerting rules, and structure comprehensive monitoring dashboards. Essential for establishing robust SRE practices and documenting system health standards.