Agent development can fail when guidance does not match the installed eve version. This skill directs your assistant to bundled documentation before project changes.

Ponytail users need a clear reference for modes, commands, and configuration. This skill displays that reference once without changing modes or saving state.

Selecting suitable partners and coordinating joint campaigns requires clear priorities and shared expectations. This skill structures partner evaluation, campaign ideas, outreach, responsibilities, and measurement.

Supplier bank change requests can redirect payments to an unverified account. This skill uses Jithox MCP checks to compare IBANs and identify cases requiring independent confirmation.

NestJS changes can introduce incompatible syntax, hidden side effects, and public API regressions. This skill guides repository inspection, focused implementation, and evidence-based verification.

Unclear responsibilities and unnecessary abstractions make NestJS code difficult to change and test. This skill guides evidence-based object design, pattern selection, and behavior-preserving refactoring.

Mixed changes and unclear publication requests can produce misleading commits or unintended remote updates. This skill guides verified Git changes and accurate messages within authorized scope.

NestJS runtime changes can create latency, security, and deployment failures when teams lack clear contracts and measurements. This skill guides component selection, bottleneck diagnosis, and reliable implementation using repository evidence and focused tests.

Source code alone cannot establish whether a NestJS feature satisfies its roadmap. This skill compares requirements with revision-specific evidence and reports completed work, gaps, legacy paths, bugs, and blockers.

NestJS repositories can hide boundary flaws and runtime risks that lint results alone cannot reveal. This skill combines local evidence collection and semantic review into one prioritized report.

Unclear module boundaries make NestJS changes harder to test and coordinate. This skill guides evidence-based architecture decisions, explicit ownership, and incremental boundary repairs.

Generic interface drafts often lack clear visual priorities and meaningful alternatives. Oil UI guides design exploration, prototype comparison, and refinement using actual screen evidence.

Security fixes can fail when verification uses stale code or broken test harnesses. This skill guides minimal patches with snapshot checks, baseline tests, and independent re-attacks.

Useful workflow lessons disappear between work sessions. Task Observer records reusable observations and guides reviews that produce staged skill updates.

Long security reviews require coordinated specialist stages and reliable campaign state across repeated passes. This skill supervises Mantis subagents, preserves findings, and manages optional synchronization and snapshot provenance.

Repeated security findings increase review effort and can obscure regressions. This skill guides consolidation while preserving provenance, active regression candidates, and transaction history.

Interactive line illustrations require consistent geometry, motion, and visual checks. This skill guides concept selection, builds a standalone HTML figure, and checks its structure and appearance.

Architecture notes often leave attacker access and trust boundaries unclear. This skill turns existing Mantis knowledge into a structured threat model with deployment intent and snapshot provenance.

Past security fixes are difficult to track across repository history. This skill guides an AI agent to extract, classify, and cache historical vulnerabilities for later analysis.

Large source trees make symbol navigation and caller discovery expensive. This skill guides structural indexing with reusable caches and coverage-aware queries while preserving lexical discovery.