Testing
Unit tests, integration tests, test automation
deft-directive-pre-pr
by deftai
Iterative pre-PR quality improvement loop. Use before pushing a branch for PR creation -- after completing implementation but before task check. Cycles through Read-Write-Lint-Diff until a full pass produces zero changes.
ux-design-sprint
by geekatron
"AJ&Smart Design Sprint 2.0 facilitation sub-skill for the /user-experience parent skill. Facilitates a structured four-day rapid prototyping and validation process compressed from the Google Ventures five-day Design Sprint (Knapp, Zeratsky & Kowitz, 2016; Courtney, 2019). Produces sprint artifacts including challenge maps, solution sketches, storyboards, realistic prototypes, and structured user interview findings with synthesis confidence gates. Invoke when teams need to rapidly validate a product concept, solve a critical design challenge through structured prototyping, test ideas with real users before committing to development, or explore solution directions when they do not know what to build. Triggers: design sprint, GV sprint, rapid prototyping, sprint week, map sketch decide test, 4-day sprint, design sprint 2.0, AJ Smart sprint, validate prototype, test with users, sprint facilitation."
wendy-contributing
by Joannis
'Expert guidance on contributing to WendyOS: Yocto builds, agent internals, E2E testing, and system architecture. Use when developers mention: (1) building WendyOS images, (2) meta-wendyos layers or bitbake, (3) wendy-agent development or internals, (4) containerd or nerdctl on WendyOS, (5) E2E tests for wendy-agent, (6) Yocto recipes or bbappend files, (7) mDNS/Avahi service configuration, (8) device identity or UUID generation.'
saucer-boy-framework-voice
by geekatron
"INTERNAL SKILL — auto-loaded for framework output voice quality. Reviews, rewrites, and scores framework output text for persona compliance using the Shane McConkey ethos: joy and excellence as multipliers. Governs quality gate messages, error messages, CLI output, hook text, and framework-generated text. Not user-invocable; loaded automatically when framework output needs voice enforcement."
deft-directive-probe
by deftai
Adversarial one-question-per-turn plan stress-testing before vBRIEF or plan artifacts. Use when the operator asks to run probe or stress-test a plan.
tactical-ddd
by NTCoding
"Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design. Triggers on: domain modeling, aggregate design, 'entity', 'value object', 'repository', 'bounded context', 'domain event', 'domain service', code touching domain/ directories, rich domain model discussions."
writing-tests
by NTCoding
"Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic. Triggers on: writing any test, 'add tests', test review, test naming, assertion choices, edge case coverage, 'what should I test', test structure decisions."
critical-peer-personality
by NTCoding
"Professional, skeptical communication style. Never over-enthusiastic, verifies before agreeing, challenges constructively, proposes instead of asking preferences. Expert peer who coaches, not serves. Triggers on: composing responses, agreeing with user, making recommendations, giving feedback."
example-skill
by RafaelGorski
This is a valid example skill for testing purposes
receiving-code-review
by TechDufus
"How to handle code review feedback with technical rigor. Use when receiving review comments from code-reviewer agent, PR reviews, or external feedback. Triggers on: 'review feedback', 'address review', 'fix review comments', 'code review response'."
publish
by colonyops
This skill should be used when the user asks to "send message to agent X", "publish to topic", "broadcast to all agents", "notify other sessions", "tell agent Y that...", or needs to send inter-agent messages, hand off work, or broadcast notifications across hive sessions.
go-senior-developer
by metalagman
Expert senior-level Go guidance for architecture, API-first design/codegen, advanced concurrency, performance tuning, testing/quality, cloud-native 12-factor practices, and Go 1.24+ tooling for large-scale systems.
atelier-spec-methodology
by martinffx
AgentOS 3-layer context, orchestrated delegation, and OpenSpec living specifications. Use when explaining how context flows through layers, how agents collaborate, or how specs evolve.
elixir-thinking
by georgeguimaraes
This skill should be used when the user asks to "implement a feature in Elixir", "refactor this module", "should I use a GenServer here?", "how should I structure this?", "use the pipe operator", "add error handling", "make this concurrent", or mentions protocols, behaviours, pattern matching, with statements, comprehensions, structs, or coming from an OOP background. Contains paradigm-shifting insights.
structure-first
by perhapsspy
Readable primary-flow–first code structuring with minimal boundaries, atomic composition, and contract-driven unit tests
dotnet-testing-autofixture-customization
by kevintsengtw
AutoFixture 進階自訂化技術完整指南。當需要自訂 AutoFixture 建構器或處理特殊型別的測試資料產生規則時使用。涵蓋 DataAnnotations 自動整合、ISpecimenBuilder 實作、優先順序管理。包含 DateTime/數值範圍建構器、泛型化設計與流暢式擴充方法。 Keywords: autofixture customization, autofixture customize, autofixture 自訂, specimen builder, ISpecimenBuilder, RandomDateTimeSequenceGenerator, NumericRangeBuilder, DataAnnotations autofixture, fixture.Customizations, Insert(0), 自訂建構器, NoSpecimen, 泛型化建構器
dotnet-testing-bogus-fake-data
by kevintsengtw
使用 Bogus 產生擬真假資料的專門技能。當需要產生真實感的姓名、地址、電話、Email、公司資訊等測試資料時使用。涵蓋 Faker 類別、多語言支援、自訂規則、大量資料產生等。 Keywords: bogus, faker, fake data, 假資料, 擬真資料, realistic data, fake name, fake address, fake email, Faker<T>, RuleFor, Generate, faker.Name, faker.Address, faker.Internet, 產生假資料, generate fake data, seed data
dotnet-testing-private-internal-testing
by kevintsengtw
Private 與 Internal 成員測試策略指南。當需要測試私有或內部成員、設定 InternalsVisibleTo 或評估可測試性設計時使用。涵蓋設計優先思維、反射測試、策略模式重構、AbstractLogger 模式與決策框架。 Keywords: private method testing, internal testing, InternalsVisibleTo, 私有方法測試, 內部成員測試, 反射測試, reflection testing, GetMethod BindingFlags, Meziantou.MSBuild.InternalsVisibleTo, 可測試性設計, 策略模式重構, testability
futurist-analyst
by rysweet
Analyzes events through futures lens using scenario planning, trend analysis, weak signals, drivers of change, and forecasting methods (exploratory, normative, backcasting). Provides insights on possible futures, emerging trends, disruptive forces, strategic foresight, and alternative scenarios. Use when: Strategic planning, emerging trends, technology assessment, long-term planning, uncertainty navigation. Evaluates: Trends, weak signals, drivers of change, plausible futures, strategic options, uncertainty ranges.
module-spec-generator
by rysweet
Generates module specifications following amplihack's brick philosophy template. Use when creating new modules or documenting existing ones to ensure they follow the brick & studs pattern. Analyzes code to extract: purpose, public contract, dependencies, test requirements.
indigenous-leader-analyst
by rysweet
Analyzes events through indigenous knowledge systems using relational thinking, seven generations principle, reciprocity, holistic integration, and traditional ecological knowledge frameworks. Provides insights on interconnectedness, long-term sustainability, collective wisdom, and decolonial perspectives. Use when: Environmental decisions, resource stewardship, community governance, decolonization, intergenerational planning. Evaluates: Relationships, sustainability, collective impact, indigenous rights, traditional knowledge integration.
owasp-ai-testing
by mastepanoski
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 44 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.
epidemiologist-analyst
by rysweet
Analyzes disease patterns and health events through epidemiological lens using surveillance systems, outbreak investigation methods, and disease modeling frameworks. Provides insights on disease spread, risk factors, prevention strategies, and public health interventions. Use when: Disease outbreaks, health policy evaluation, risk assessment, intervention planning. Evaluates: Transmission dynamics, risk factors, causality, population health impact, intervention effectiveness.
novelist-analyst
by rysweet
Analyzes events through narrative lens using story structure, character arc analysis, dramatic tension, thematic development, and narrative theory (three-act structure, hero's journey, conflict-resolution). Provides insights on narrative coherence, character motivations, dramatic stakes, plot development, and thematic resonance. Use when: Complex human stories, leadership analysis, organizational narratives, crisis narratives, cultural moments. Evaluates: Character development, narrative arc, dramatic tension, thematic depth, symbolic meaning, narrative coherence.