unit-testing-csharp
Implementar pruebas unitarias para proyectos C# utilizando Clean Architecture y los principios SOLID, siguiendo la metodología oficial de Adasoft con asistencia de IA. Utiliza esta habilidad siempre que el usuario solicite escribir pruebas, crear pruebas unitarias, añadir cobertura de pruebas, configurar un proyecto de pruebas, generar casos de prueba para un caso de uso o un controlador, revisar la calidad de las pruebas, corregir pruebas fallidas, simular dependencias, utilizar xUnit/FluentAssertions/NSubstitute, probar componentes Blazor con bUnit o preguntar sobre la estrategia de pruebas para cualquier proyecto C# de Adasoft. También se activa cuando el usuario menciona Red-Green-Refactor, el patrón AAA, los objetivos de cobertura de pruebas o el desarrollo basado en pruebas en un contexto C#.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that comprehensively covers what the skill does (C# unit testing with specific methodologies and tools) and when to use it (extensive list of trigger scenarios). It uses proper third-person voice, includes natural trigger terms in Spanish, and is highly distinctive due to its specific technology stack and organizational context (Adasoft). The description is thorough without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'escribir pruebas', 'crear pruebas unitarias', 'añadir cobertura de pruebas', 'configurar un proyecto de pruebas', 'generar casos de prueba', 'revisar la calidad de las pruebas', 'corregir pruebas fallidas', 'simular dependencias', 'probar componentes Blazor'. Also names specific tools: xUnit, FluentAssertions, NSubstitute, bUnit. | 3 / 3 |
Completeness | Clearly answers both what (implement unit tests for C# projects using Clean Architecture and SOLID principles) AND when with explicit 'Utiliza esta habilidad siempre que...' clause followed by comprehensive trigger scenarios. The 'También se activa cuando...' adds additional explicit trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'escribir pruebas', 'crear pruebas unitarias', 'cobertura de pruebas', 'casos de prueba', 'pruebas fallidas', 'Red-Green-Refactor', 'patrón AAA', 'desarrollo basado en pruebas', plus specific tool names and framework references that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche: C# unit testing specifically for Adasoft projects with Clean Architecture. The combination of language (C#), methodology (Adasoft), architecture pattern (Clean Architecture), and specific tooling (xUnit/FluentAssertions/NSubstitute/bUnit) creates a distinct identity unlikely to conflict with general testing or other language testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently communicates Adasoft's unit testing methodology. It provides actionable guidance with executable code, clear decision trees, and explicit validation checklists. The content respects Claude's intelligence while adding project-specific conventions and standards.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code examples without explaining concepts Claude already knows. Every section adds specific value for Adasoft's methodology without padding. | 3 / 3 |
Actionability | Provides fully executable code examples with xUnit/NSubstitute/FluentAssertions, specific naming conventions, and a concrete checklist. The code is copy-paste ready and follows real patterns. | 3 / 3 |
Workflow Clarity | Clear decision tree before writing tests, explicit Red-Green-Refactor cycle, and a comprehensive validation checklist with explicit checkpoints. The 'refactorizar primero' gates prevent proceeding with untestable code. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections, and appropriately references external files (bunit-blazor.md, examples.md) for detailed content. One-level-deep references are clearly signaled at the end. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- lBuitronAdasoft/TmpSkills
- Commit
0202bb8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.