All authors
Claude Skills by tensology
github.com/tensology354 skills1 installs302 views
- Recursive Decision LedgerUse when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.Votes: 0GitHub stars: 17
- Redis PatternsRedis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications.Votes: 0GitHub stars: 17
- Repo ScanCross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.Votes: 0GitHub stars: 17
- Returns Reverse LogisticsCodified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.Votes: 0GitHub stars: 17
- Safety GuardUse this skill to prevent destructive operations when working on production systems or running agents autonomously.Votes: 0GitHub stars: 17
- Scientific Db Pubmed DatabaseDirect PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.Votes: 0GitHub stars: 17
- Security Bounty HunterHunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.Votes: 0GitHub stars: 17
- SeoAudit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy. Use when the user wants better search visibility, SEO remediation, schema markup, sitemap/robots work, or keyword mapping.Votes: 0GitHub stars: 17
- Skill ScoutSearch existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.Votes: 0GitHub stars: 17
- Social Graph RankerWeighted social-graph ranking for warm intro discovery, bridge scoring, and network gap analysis across X and LinkedIn. Use when the user wants the reusable graph-ranking engine itself, not the broader outreach or network-maintenance workflow layered on top of it.Votes: 0GitHub stars: 17
- Team BuilderInteractive agent picker for composing and dispatching parallel teamsVotes: 0GitHub stars: 17
- Terminal OpsEvidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.Votes: 0GitHub stars: 17
- Tinystruct PatternsExpert guidance for developing with the tinystruct Java framework. Use when working on the tinystruct codebase or any project built on tinystruct — including creating Application classes, @Action-mapped routes, unit tests, ActionRegistry, HTTP/CLI dual-mode handling, the built-in HTTP server, the event system, JSON with Builder/Builders, database persistence with AbstractData, POJO generation, Server-Sent Events (SSE), file uploads, and outbound HTTP networking.Votes: 0GitHub stars: 17
- Token Budget AdvisorOffers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero contro...Votes: 0GitHub stars: 17
- Ui DemoRecord polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.Votes: 0GitHub stars: 17
- UncloudUse when managing an Uncloud cluster — deploying services, configuring Caddy ingress, adding static proxy routes for non-cluster devices, publishing ports, scaling, inspecting logs, or managing machines and volumes with the `uc` CLI.Votes: 0GitHub stars: 17
- Unified Notifications OpsOperate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.Votes: 0GitHub stars: 17
- Vite PatternsVite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.Votes: 0GitHub stars: 17
- Windows Desktop E2eE2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation.Votes: 0GitHub stars: 17
- Workspace Surface AuditAudit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.Votes: 0GitHub stars: 17
- X ApiX/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.Votes: 0GitHub stars: 17
- Decisions Computer UseUse native computer-use safely in Decisions workflows when the active harness exposes a CUA or computer-use runtime.Votes: 0GitHub stars: 17
- BasicPrint-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.Votes: 0GitHub stars: 17
- CleanSimplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.Votes: 0GitHub stars: 17
- ImpeccableA modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.Votes: 0GitHub stars: 17
- SleekModern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing.Votes: 0GitHub stars: 17
- Plan ArbiterUse when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.Votes: 0GitHub stars: 17
- Plow AheadUse when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done", "finish while I am away", "do not ask questions unless truly blocked", or similar. Convert ordinary ambiguity into stated assumptions, proceed through implementation and validation, stop only for true blockers, and end with a clear recap of decisions, changes, verification, and residual risk.Votes: 0GitHub stars: 17
- Read The Damn DocsUse when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces Codex to web-search for current official docs and read primary docs ...Votes: 0GitHub stars: 17
- Stay Within LimitsUse when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.Votes: 0GitHub stars: 17
- AutoplanAuto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wan...Votes: 0GitHub stars: 17
- CarefulSafety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". (gstack)Votes: 0GitHub stars: 17
- Design ConsultationDesign consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design syste...Votes: 0GitHub stars: 17
- Design HtmlDesign finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "impleme...Votes: 0GitHub stars: 17
- InvestigateSystematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)Votes: 0GitHub stars: 17
- Plan Design ReviewDesigner's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation. (gstack)Votes: 0GitHub stars: 17
- Qa OnlyReport-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".Votes: 0GitHub stars: 17
- QaSystematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix ...Votes: 0GitHub stars: 17
- Taste DesignSemantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.Votes: 0GitHub stars: 17
- Cart LifecycleUse when designing cart identity, persistence, merging, revalidation, expiry, or the transition from anonymous browsing to checkout. Load before deciding how guest carts attach to accounts on login, how prices/inventory refresh as the cart ages, or how the cart converts into an order. Vocabulary (cart, line item, customer, account, guest, variant, available, reserved, quote, order) is imported from domain-vocabulary.Votes: 0GitHub stars: 17
- Catalog And Product ModelingUse when designing or modifying the catalog data model — defining how products, variants, SKUs, attributes, options, categories, taxonomies, collections, and media relate. Load before creating product tables, deciding whether a configurable item should be one product with variants or many products, structuring category hierarchies, or wiring SEO slugs. Vocabulary is imported from the domain-vocabulary skill.Votes: 0GitHub stars: 17
- Domain VocabularyUse when reasoning about any ecommerce system — establishes authoritative definitions for cart, quote, order, line item, on-hand, available, reserved, committed, customer, account, variant, SKU, channel, authorization, capture, fulfillment, shipment, and the other terms every other skill in this package depends on. Load this skill before discussing commerce primitives, designing data models, naming entities, or resolving ambiguity in requirements.Votes: 0GitHub stars: 17
- IdempotencyUse when designing any operation that may be retried — HTTP POST endpoints, payment requests, webhook consumers, message handlers, async job enqueues, integration calls. Load before deciding whether an operation needs an idempotency key, how to generate the key, how long to keep replay state, or what to return on replay. Vocabulary (idempotency key, idempotent operation, replay, CIT, MIT) is established here; cross-references domain-vocabulary, payment-flows, webhooks, order-lifecycle.Votes: 0GitHub stars: 17
- Inventory ManagementUse when designing stock tracking, reservation timing, oversell policy, multi-location allocation, or any code that decrements/holds inventory. Load before writing the function that checks "is this in stock", choosing when to deduct stock in the cart-to-order flow, or modeling stock across warehouses. Vocabulary (on-hand, available, reserved, committed, safety stock, location, backorder, oversell) is imported from domain-vocabulary.Votes: 0GitHub stars: 17
- Order LifecycleUse when designing the order state machine, allowed transitions, side effects per transition, cancellation paths, refund flows, or how payment status and fulfillment status interact. Load before adding an order status field, writing a transition, or modeling sub-orders/fulfillments. Vocabulary (order, line item, cart, payment status, fulfillment status, authorization, capture, refund, void, shipment, location) is imported from domain-vocabulary.Votes: 0GitHub stars: 17
- Payment FlowsUse when integrating any payment processor or designing how the system handles authorization, capture, sale, void, refund, dispute, hosted vs embedded checkout, webhook confirmation, tokenization, and PCI scope. Load before adding a payment provider, deciding when to capture, modeling stored payment methods, or wiring 3DS/SCA. Vocabulary (authorization, capture, sale, void, refund, chargeback, hosted checkout, embedded checkout, tokenization, payment status, order) is imported from domain-voc...Votes: 0GitHub stars: 17
- Pricing And ChannelsUse when designing how prices are stored, scoped, and computed — list price vs sale price, price lists per channel/customer-group/region, multi-currency representation, tax-inclusive vs tax-exclusive display, tiered pricing, and the Money pattern. Load before adding a price column, designing a price-resolution rule, or wiring a tax-display toggle. Vocabulary is imported from domain-vocabulary.Votes: 0GitHub stars: 17
- WebhooksUse when designing webhook receivers or senders — signature verification, replay protection, retry policy, at-least-once handling, dead-letter strategy, and event payload contracts. Load before wiring an inbound webhook endpoint (payment processor, shipping carrier, marketplace), publishing outbound events to merchant integrations, or debugging missing/duplicate events. Cross-references idempotency, payment-flows, order-lifecycle.Votes: 0GitHub stars: 17
- Ponytail HelpQuick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".Votes: 0GitHub stars: 17
- Ponytail ReviewCode review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.Votes: 0GitHub stars: 17