agent-nuvira 1.88.0 → 1.88.2

package/.agents/skills/a11y-audit/references/guide.md

@@ -0,0 +1,55 @@
+# A11y Audit Reference Guide
+
+## Overview
+Audit web applications for accessibility (WCAG 2.1 AA compliance): check color contrast, keyboard navigation, screen-reader compatibility, ARIA attributes, and semantic HTML. Use when the goal asks to audit, fix, or improve accessibility.
+
+## # a11y-audit
+
+Audit web applications for accessibility (WCAG 2.1 AA compliance): check color contrast, keyboard navigation, screen-reader compatibility, ARIA attributes, and semantic HTML. Use when the goal asks to audit, fix, or improve accessibility.
+
+## Goal pattern
+
+accessibility a11y wcag audit screen reader keyboard nav aria contrast wcag
+
+## Parameters
+
+- scope (choice [default: full]): Audit scope
+
+## Steps
+
+1. [analyst] Scan the codebase for accessibility issues: run automated tools (axe-core, pa11y, lighthouse) or inspect JSX for missing alt text, labels, ARIA roles, and semantic landmarks.
+
+2. [analyst] Categorize issues by severity: critical (blocks users), serious (hard to use), moderate (annoying), minor (cosmetic). Map to WCAG success criteria. (after: step-1)
+
+3. [analyst] Fix critical and serious issues: add missing alt text, labels, ARIA attributes, keyboard handlers, focus management, and color contrast adjustments. (after: step-2)
+
+4. [analyst] Test fixes: verify keyboard-only navigation, screen-reader output, and color contrast ratios. Re-run automated scanner. (after: step-3)
+
+5. [analyst] Write an accessibility report: WCAG 2.1 AA conformance status, remaining issues by severity, and an accessibility statement for the project. (after: step-4)
+
+## Best Practices
+
+- Follow the skill's methodology step by step
+- Verify each step before proceeding to the next
+- Use the appropriate tools for each task
+- Document any deviations from the standard approach
+
+## Common Patterns
+
+- Start with context gathering to understand the current state
+- Plan the implementation before writing code
+- Test changes before committing
+- Review for security and performance implications
+
+## Troubleshooting
+
+- If the skill fails, check the prerequisites first
+- Verify environment variables are set correctly
+- Check for conflicting configurations
+- Review logs for detailed error messages
+
+## Further Reading
+
+- Refer to the main SKILL.md for complete methodology
+- Check official documentation for the specific technology
+- Review related skills in the registry for complementary approaches

package/.agents/skills/academic-research/SKILL.md

@@ -12,24 +12,28 @@ Conduct academic literature research: paper discovery, citation analysis, system
 
 academic research literature review paper citation systematic review arxiv pubmed scholar
 
+## Parameters
+
+(none)
+
 ## Steps
 
-0. [context-gatherer] Map the research topic: what field? What search terms? What databases (arXiv, PubMed, Google Scholar)? What time range? What inclusion criteria?
+1. [context-gatherer] Map the research topic: what field? What search terms? What databases (arXiv, PubMed, Google Scholar)? What time range? What inclusion criteria?
 
-1. [planner] Plan the literature review:
+2. [planner] Plan the literature review:
 1. Search strategy: keywords, boolean operators, databases
 2. Screening: title/abstract → full text selection
 3. Data extraction: methods, findings, quality assessment
 4. Synthesis: thematic analysis, meta-analysis if quantitative
 5. Citation analysis: key papers, influential authors
-6. Reporting: structured summary with gaps identified (after: 'step-0')
+6. Reporting: structured summary with gaps identified (after: step-0)
 
-2. [runner] Execute the review:
+3. [runner] Execute the review:
 1. Search databases with query strategy
 2. Screen results (title/abstract)
 3. Full-text review of selected papers
 4. Extract key findings
 5. Synthesize across papers
-6. Identify research gaps (after: 'step-1')
+6. Identify research gaps (after: step-1)
 
-3. [reviewer] Review: verify search completeness, check extraction accuracy, validate synthesis, ensure citations are correct. (after: 'step-2')
+4. [reviewer] Review: verify search completeness, check extraction accuracy, validate synthesis, ensure citations are correct. (after: step-2)

package/.agents/skills/academic-research/references/guide.md

@@ -0,0 +1,61 @@
+# Academic Research Reference Guide
+
+## Overview
+Conduct academic literature research: paper discovery, citation analysis, systematic reviews, and research summaries. Use when the goal is to review academic literature on a topic.
+
+## # academic-research
+
+Conduct academic literature research: paper discovery, citation analysis, systematic reviews, and research summaries. Use when the goal is to review academic literature on a topic.
+
+## Goal pattern
+
+academic research literature review paper citation systematic review arxiv pubmed scholar
+
+## Steps
+
+0. [context-gatherer] Map the research topic: what field? What search terms? What databases (arXiv, PubMed, Google Scholar)? What time range? What inclusion criteria?
+
+1. [planner] Plan the literature review:
+1. Search strategy: keywords, boolean operators, databases
+2. Screening: title/abstract → full text selection
+3. Data extraction: methods, findings, quality assessment
+4. Synthesis: thematic analysis, meta-analysis if quantitative
+5. Citation analysis: key papers, influential authors
+6. Reporting: structured summary with gaps identified (after: 'step-0')
+
+2. [runner] Execute the review:
+1. Search databases with query strategy
+2. Screen results (title/abstract)
+3. Full-text review of selected papers
+4. Extract key findings
+5. Synthesize across papers
+6. Identify research gaps (after: 'step-1')
+
+3. [reviewer] Review: verify search completeness, check extraction accuracy, validate synthesis, ensure citations are correct. (after: 'step-2')
+
+## Best Practices
+
+- Follow the skill's methodology step by step
+- Verify each step before proceeding to the next
+- Use the appropriate tools for each task
+- Document any deviations from the standard approach
+
+## Common Patterns
+
+- Start with context gathering to understand the current state
+- Plan the implementation before writing code
+- Test changes before committing
+- Review for security and performance implications
+
+## Troubleshooting
+
+- If the skill fails, check the prerequisites first
+- Verify environment variables are set correctly
+- Check for conflicting configurations
+- Review logs for detailed error messages
+
+## Further Reading
+
+- Refer to the main SKILL.md for complete methodology
+- Check official documentation for the specific technology
+- Review related skills in the registry for complementary approaches

package/.agents/skills/accounting-integration/SKILL.md

@@ -12,24 +12,28 @@ Integrate accounting software: QuickBooks, Xero, or FreshBooks API integration f
 
 accounting quickbooks xero freshbooks invoice expense financial reporting integration API
 
+## Parameters
+
+(none)
+
 ## Steps
 
-0. [context-gatherer] Map the integration: what accounting platform? What data to sync (invoices, expenses, customers, products)? Sync direction (bidirectional, push, pull)? Frequency?
+1. [context-gatherer] Map the integration: what accounting platform? What data to sync (invoices, expenses, customers, products)? Sync direction (bidirectional, push, pull)? Frequency?
 
-1. [planner] Design the integration:
+2. [planner] Design the integration:
 1. Auth: OAuth2 flow for API access
 2. Data mapping: your models → accounting platform models
 3. Sync: create/update invoices, expenses, contacts
 4. Webhooks: receive updates from accounting platform
 5. Error handling: retry, conflict resolution
-6. Reporting: pull financial data for dashboards (after: 'step-0')
+6. Reporting: pull financial data for dashboards (after: step-0)
 
-2. [runner] Implement the integration:
+3. [runner] Implement the integration:
 1. Set up OAuth2 authentication
 2. Create API client for the accounting platform
 3. Implement data sync functions
 4. Add webhook handlers
 5. Build conflict resolution logic
-6. Test with sandbox account (after: 'step-1')
+6. Test with sandbox account (after: step-1)
 
-3. [reviewer] Verify: create invoice via API, verify it appears in accounting platform, test expense sync, verify financial reports pull correctly. (after: 'step-2')
+4. [reviewer] Verify: create invoice via API, verify it appears in accounting platform, test expense sync, verify financial reports pull correctly. (after: step-2)

package/.agents/skills/accounting-integration/references/guide.md

@@ -0,0 +1,61 @@
+# Accounting Integration Reference Guide
+
+## Overview
+Integrate accounting software: QuickBooks, Xero, or FreshBooks API integration for invoices, expenses, and financial reporting. Use when the goal is to sync financial data with an accounting system.
+
+## # accounting-integration
+
+Integrate accounting software: QuickBooks, Xero, or FreshBooks API integration for invoices, expenses, and financial reporting. Use when the goal is to sync financial data with an accounting system.
+
+## Goal pattern
+
+accounting quickbooks xero freshbooks invoice expense financial reporting integration API
+
+## Steps
+
+0. [context-gatherer] Map the integration: what accounting platform? What data to sync (invoices, expenses, customers, products)? Sync direction (bidirectional, push, pull)? Frequency?
+
+1. [planner] Design the integration:
+1. Auth: OAuth2 flow for API access
+2. Data mapping: your models → accounting platform models
+3. Sync: create/update invoices, expenses, contacts
+4. Webhooks: receive updates from accounting platform
+5. Error handling: retry, conflict resolution
+6. Reporting: pull financial data for dashboards (after: 'step-0')
+
+2. [runner] Implement the integration:
+1. Set up OAuth2 authentication
+2. Create API client for the accounting platform
+3. Implement data sync functions
+4. Add webhook handlers
+5. Build conflict resolution logic
+6. Test with sandbox account (after: 'step-1')
+
+3. [reviewer] Verify: create invoice via API, verify it appears in accounting platform, test expense sync, verify financial reports pull correctly. (after: 'step-2')
+
+## Best Practices
+
+- Follow the skill's methodology step by step
+- Verify each step before proceeding to the next
+- Use the appropriate tools for each task
+- Document any deviations from the standard approach
+
+## Common Patterns
+
+- Start with context gathering to understand the current state
+- Plan the implementation before writing code
+- Test changes before committing
+- Review for security and performance implications
+
+## Troubleshooting
+
+- If the skill fails, check the prerequisites first
+- Verify environment variables are set correctly
+- Check for conflicting configurations
+- Review logs for detailed error messages
+
+## Further Reading
+
+- Refer to the main SKILL.md for complete methodology
+- Check official documentation for the specific technology
+- Review related skills in the registry for complementary approaches

package/.agents/skills/api-call/references/guide.md

@@ -0,0 +1,53 @@
+# Api Call Reference Guide
+
+## Overview
+Make API calls with authentication, retry logic, and response parsing
+
+## # API Call Skill
+
+Make API calls with authentication, retry logic, and response parsing. This skill demonstrates the execution engine's ability to run Node.js scripts.
+
+## How It Works
+
+1. Receives endpoint, method, and optional data/headers
+2. Makes HTTP request to API_BASE_URL + endpoint
+3. Handles authentication via API_KEY environment variable
+4. Implements retry logic with exponential backoff
+5. Returns structured response
+
+## Usage
+
+When the user needs to make an API call, execute this skill with the endpoint and method.
+
+## Security
+
+- API keys are injected via environment variables
+- Base URL is configured via API_BASE_URL
+- Retry logic prevents excessive requests
+
+## Best Practices
+
+- Follow the skill's methodology step by step
+- Verify each step before proceeding to the next
+- Use the appropriate tools for each task
+- Document any deviations from the standard approach
+
+## Common Patterns
+
+- Start with context gathering to understand the current state
+- Plan the implementation before writing code
+- Test changes before committing
+- Review for security and performance implications
+
+## Troubleshooting
+
+- If the skill fails, check the prerequisites first
+- Verify environment variables are set correctly
+- Check for conflicting configurations
+- Review logs for detailed error messages
+
+## Further Reading
+
+- Refer to the main SKILL.md for complete methodology
+- Check official documentation for the specific technology
+- Review related skills in the registry for complementary approaches

package/.agents/skills/api-creation/SKILL.md

@@ -14,50 +14,50 @@ API create build backend service REST GraphQL HTTP server routes endpoints imple
 
 ## Parameters
 
-- framework (choice [default: auto]): HTTP framework — express, fastify, hono, flask, fastapi, spring, auto
-- database (choice [default: auto]): Database — postgresql, mongodb, sqlite, mysql, in-memory, auto
-- auth (choice [default: jwt]): Authentication method — jwt, api-key, oauth2, session, none
+- framework (choice [default: auto]): HTTP framework (auto-detected from project)
+- database (choice [default: auto]): Database to use
+- auth (choice [default: jwt]): Authentication method
 
 ## Steps
 
 1. [context-gatherer] Analyze the project and API requirements:
-   - Read package.json / pyproject.toml for framework (Express, Fastify, Hono, Flask, FastAPI, Spring Boot)
-   - Identify resources (nouns → endpoints) and operations (CRUD)
-   - Note auth requirements (API key, JWT, OAuth2)
-   - Note database (PostgreSQL, MongoDB, SQLite, in-memory)
-   - Note deployment target (local, Docker, cloud)
-   Produce: resource list, framework choice, auth strategy, and database plan.
+- Read package.json / pyproject.toml for framework (Express, Fastify, Hono, Flask, FastAPI, Spring Boot)
+- Identify resources (nouns → endpoints) and operations (CRUD)
+- Note auth requirements (API key, JWT, OAuth2)
+- Note database (PostgreSQL, MongoDB, SQLite, in-memory)
+- Note deployment target (local, Docker, cloud)
+Produce: resource list, framework choice, auth strategy, and database plan.
 
 2. [writer] Implement the API:
-   - Set up the project structure (routes/, models/, middleware/, utils/)
-   - Implement route handlers for each resource
-   - Add input validation (Joi, Zod, Pydantic, express-validator)
-   - Add error handling middleware (consistent error response format)
-   - Add auth middleware (JWT verification, API key check)
-   - Add rate limiting (express-rate-limit, slowapi)
-   - Wire everything into the app entry point
-   Follow REST conventions: proper HTTP methods, status codes, and response shapes.
+- Set up the project structure (routes/, models/, middleware/, utils/)
+- Implement route handlers for each resource
+- Add input validation (Joi, Zod, Pydantic, express-validator)
+- Add error handling middleware (consistent error response format)
+- Add auth middleware (JWT verification, API key check)
+- Add rate limiting (express-rate-limit, slowapi)
+- Wire everything into the app entry point
+Follow REST conventions: proper HTTP methods, status codes, and response shapes. (after: step-0)
 
 3. [writer] Generate OpenAPI/Swagger documentation:
-   - Create openapi.yaml or openapi.json with all endpoints
-   - Define request/response schemas
-   - Add authentication definitions
-   - Add example requests and responses
-   - Set up Swagger UI (if web framework supports it)
-   The spec is the contract — implementation must match it exactly.
+- Create openapi.yaml or openapi.json with all endpoints
+- Define request/response schemas
+- Add authentication definitions
+- Add example requests and responses
+- Set up Swagger UI (if web framework supports it)
+The spec is the contract — implementation must match it exactly. (after: step-1)
 
 4. [tester] Write and run integration tests:
-   - Test each endpoint: happy path, error paths (400, 401, 404, 500)
-   - Test auth: unauthenticated → 401, unauthorized → 403
-   - Test validation: invalid input → 400 with error details
-   - Test edge cases: empty body, missing fields, duplicate resources
-   - Run the full test suite: `npm test` or `pytest`
-   All tests must pass before proceeding.
+- Test each endpoint: happy path, error paths (400, 401, 404, 500)
+- Test auth: unauthenticated → 401, unauthorized → 403
+- Test validation: invalid input → 400 with error details
+- Test edge cases: empty body, missing fields, duplicate resources
+- Run the full test suite: `npm test` or `pytest`
+All tests must pass before proceeding. (after: step-2)
 
 5. [runner] Set up deployment:
-   - Create Dockerfile (multi-stage build)
-   - Create docker-compose.yml (if database needed)
-   - Add health check endpoint (GET /health)
-   - Add environment variable configuration
-   - Create a README with API documentation and usage examples
-   - Verify the app starts and responds to requests
+- Create Dockerfile (multi-stage build)
+- Create docker-compose.yml (if database needed)
+- Add health check endpoint (GET /health)
+- Add environment variable configuration
+- Create a README with API documentation and usage examples
+- Verify the app starts and responds to requests (after: step-3)

package/.agents/skills/api-creation/references/guide.md

@@ -0,0 +1,89 @@
+# Api Creation Reference Guide
+
+## Overview
+Create a complete API: design endpoints, implement routes, add auth/rate-limiting, write tests, generate OpenAPI docs, and deploy. Use when the goal asks to create an API, build a backend service, or scaffold an HTTP server with routes.
+
+## # api-creation
+
+Create a complete API: design endpoints, implement routes, add auth/rate-limiting, write tests, generate OpenAPI docs, and deploy. Use when the goal asks to create an API, build a backend service, or scaffold an HTTP server with routes.
+
+## Goal pattern
+
+API create build backend service REST GraphQL HTTP server routes endpoints implement deploy
+
+## Parameters
+
+- framework (choice [default: auto]): HTTP framework — express, fastify, hono, flask, fastapi, spring, auto
+- database (choice [default: auto]): Database — postgresql, mongodb, sqlite, mysql, in-memory, auto
+- auth (choice [default: jwt]): Authentication method — jwt, api-key, oauth2, session, none
+
+## Steps
+
+1. [context-gatherer] Analyze the project and API requirements:
+   - Read package.json / pyproject.toml for framework (Express, Fastify, Hono, Flask, FastAPI, Spring Boot)
+   - Identify resources (nouns → endpoints) and operations (CRUD)
+   - Note auth requirements (API key, JWT, OAuth2)
+   - Note database (PostgreSQL, MongoDB, SQLite, in-memory)
+   - Note deployment target (local, Docker, cloud)
+   Produce: resource list, framework choice, auth strategy, and database plan.
+
+2. [writer] Implement the API:
+   - Set up the project structure (routes/, models/, middleware/, utils/)
+   - Implement route handlers for each resource
+   - Add input validation (Joi, Zod, Pydantic, express-validator)
+   - Add error handling middleware (consistent error response format)
+   - Add auth middleware (JWT verification, API key check)
+   - Add rate limiting (express-rate-limit, slowapi)
+   - Wire everything into the app entry point
+   Follow REST conventions: proper HTTP methods, status codes, and response shapes.
+
+3. [writer] Generate OpenAPI/Swagger documentation:
+   - Create openapi.yaml or openapi.json with all endpoints
+   - Define request/response schemas
+   - Add authentication definitions
+   - Add example requests and responses
+   - Set up Swagger UI (if web framework supports it)
+   The spec is the contract — implementation must match it exactly.
+
+4. [tester] Write and run integration tests:
+   - Test each endpoint: happy path, error paths (400, 401, 404, 500)
+   - Test auth: unauthenticated → 401, unauthorized → 403
+   - Test validation: invalid input → 400 with error details
+   - Test edge cases: empty body, missing fields, duplicate resources
+   - Run the full test suite: `npm test` or `pytest`
+   All tests must pass before proceeding.
+
+5. [runner] Set up deployment:
+   - Create Dockerfile (multi-stage build)
+   - Create docker-compose.yml (if database needed)
+   - Add health check endpoint (GET /health)
+   - Add environment variable configuration
+   - Create a README with API documentation and usage examples
+   - Verify the app starts and responds to requests
+
+## Best Practices
+
+- Follow the skill's methodology step by step
+- Verify each step before proceeding to the next
+- Use the appropriate tools for each task
+- Document any deviations from the standard approach
+
+## Common Patterns
+
+- Start with context gathering to understand the current state
+- Plan the implementation before writing code
+- Test changes before committing
+- Review for security and performance implications
+
+## Troubleshooting
+
+- If the skill fails, check the prerequisites first
+- Verify environment variables are set correctly
+- Check for conflicting configurations
+- Review logs for detailed error messages
+
+## Further Reading
+
+- Refer to the main SKILL.md for complete methodology
+- Check official documentation for the specific technology
+- Review related skills in the registry for complementary approaches