all publishers

JovaniPink

@jovanipink source repo

262 published skills · page 2 of 3

  1. ▌
    Multi Agent Orchestration 3 · jovanipink bundle
    Coordinate authorized parallel agents on independent bounded tasks with explicit ownership, evidence contracts, cost awareness, and final reconciliation. Invoke explicitly when parallel work can reduce latency without creating edit collisions or delegating irreversible decisions.
    1 repo stars
  2. ▌
    Acceptance Evidence Ledger 3 · jovanipink bundle
    Create or update an acceptance ledger for substantial work that needs explicit outcomes, current evidence, re-verification, and visible blockers or abandonments. Invoke explicitly when a user requests an inline or repository-owned completion contract; use focused testing, execution, or claim-verification skills for one-time requests.
    1 repo stars
  3. ▌
    Research To Publication Lifecycle 3 · jovanipink bundle
    Coordinate an explicitly requested source-to-publication learning lifecycle across research, evidence tracing, model or forecast evaluation, corrections, and retrospective findings. Invoke explicitly when the user wants traceable knowledge objects or a public-safe research index; do not use for a one-off search, ordinary summary, or automatic publication.
    1 repo stars
  4. ▌
    Merge Conflict Reconciliation 3 · jovanipink
    Reconcile an active Git merge, rebase, or cherry-pick conflict by inspecting exact repository state, preserving both sides' intent, validating the result, and keeping abort available. Invoke explicitly for an identified conflicted worktree; staging, continuing, committing, and pushing require separate authority.
    1 repo stars
  5. ▌
    Task Handoff 2 · jovanipink bundle
    Prepare a precise handoff for continuing work in another session, client, person, or agent using exact revisions, current state, evidence, decisions, blockers, and authority boundaries. Invoke explicitly when continuity matters and the recipient must not rediscover or overstate progress.
    1 repo stars
  6. ▌
    Test Strategy 2 · jovanipink
    Design risk-proportionate test coverage across unit, integration, contract, end-to-end, property, migration, and manual layers. Use when a feature, architecture change, or defect needs a justified coverage plan rather than only running existing checks.
    1 repo stars
  7. ▌
    Claim Verification 2 · jovanipink bundle
    Verify claims that work is complete, broken, missing, merged, deployed, or live by checking the relevant repository and platform evidence. Use when a review, handoff, PR, agent, or collaborator makes claims that would materially change the next action.
    1 repo stars
  8. ▌
    Plan Execution 2 · jovanipink bundle
    Execute a named, approved implementation plan with checkpoints, validation, deviation tracking, and strict stopping boundaries. Invoke explicitly when the user authorizes implementation against an identified plan.
    1 repo stars
  9. ▌
    Prelaunch Readiness 2 · jovanipink bundle
    Audit whether a web property, service, application, or major relaunch is ready for public use, separating repository checks from provider and live-runtime evidence. Use for launch checklists, release readiness, and go or no-go reviews.
    1 repo stars
  10. ▌
    Prototype Spike 2 · jovanipink bundle
    Run a bounded prototype or technical spike to answer a named uncertainty with disposable or isolated work and explicit evidence. Invoke explicitly when the user authorizes implementation for learning but has not authorized production adoption, merge, or release.
    1 repo stars
  11. ▌
    Problem Framing 2 · jovanipink
    Frame a proposed feature, defect, workflow, or system change before implementation by identifying users, outcomes, evidence, constraints, unknowns, options, and measurable success. Use when a request is important but the problem or desired result is not yet decision-ready.
    1 repo stars
  12. ▌
    Systematic Diagnosis 2 · jovanipink
    Diagnose a defect, failure, regression, or confusing behavior by reproducing it, narrowing the causal boundary, and reporting evidence. Use when the user asks why something fails or requests diagnosis without necessarily authorizing a fix.
    1 repo stars
  13. ▌
    Publish Change Safely 2 · jovanipink bundle
    Publish an authorized repository change by verifying identity, remote, branch, diff scope, checks, commit, push, PR state, and repository visibility. Use only when the user explicitly asks to commit, push, publish, or open a pull request.
    1 repo stars
  14. ▌
    Skill Security Review 2 · jovanipink bundle
    Audit an agent skill or plugin for prompt manipulation, unsafe commands, file and network blast radius, dependencies, hooks, permissions, data exposure, and deceptive behavior. Use before installing, promoting, or updating third-party or high-impact skills.
    1 repo stars
  15. ▌
    Alignment Interview 2 · jovanipink bundle
    Establish a shared, decision-ready understanding before implementation by inspecting available evidence and asking one material question at a time. Use when goals, constraints, terminology, or success criteria are unclear; do not use to delay an already approved and sufficiently specified change.
    1 repo stars
  16. ▌
    Guided Configuration 2 · jovanipink bundle
    Guide a person through configuration steps that require their account, device, approval, credential, or external interface while verifying each observable result. Invoke explicitly when the agent cannot or should not perform the protected step itself.
    1 repo stars
  17. ▌
    Skill Import Provenance 2 · jovanipink bundle
    Review provenance before transferring Jovani-owned skill material between authorized repositories or distributions. Invoke explicitly for an owned-source transfer or a decision about whether proposed external skill material must be rejected; third-party skill catalogs are never implementation sources.
    1 repo stars
  18. ▌
    Code Change Review 2 · jovanipink
    Review an exact code change for correctness, regressions, security, compatibility, test quality, and maintainability using the diff and repository evidence. Use before commit, pull request, merge, or release when the user wants findings rather than implementation.
    1 repo stars
  19. ▌
    Test Driven Change 2 · jovanipink
    Guide feature and defect work through red, green, and refactor evidence while preserving a clear exception path when test-first work is unsuitable. Use for behavior changes where an executable test can prove the defect or desired outcome before implementation.
    1 repo stars
  20. ▌
    Worktree Isolation 2 · jovanipink bundle
    Assess whether dirty or concurrent repository work needs Git worktree isolation and design a safe isolation approach. Use when work may overlap existing changes; require explicit authority before creating, moving, locking, repairing, or removing a worktree.
    1 repo stars
  21. ▌
    Codebase Explanation 2 · jovanipink
    Explain how an existing codebase works using current repository evidence: entrypoints, ownership, control and data flow, state, interfaces, failures, and concrete files. Use when the user asks how code behaves; use design-rationale-investigation instead for historical intent or why a design was chosen.
    1 repo stars
  22. ▌
    Request Code Review 2 · jovanipink bundle
    Prepare an evidence-bounded code review packet and, only when separately authorized, send or publish the request. Invoke explicitly when a change is ready for reviewer attention and its scope, checks, risks, and unresolved decisions must be stated precisely.
    1 repo stars
  23. ▌
    Test Quality Review 2 · jovanipink
    Review the quality of a test suite or change-specific tests for meaningful assertions, defect sensitivity, isolation, determinism, risk coverage, and maintenance cost. Use when existing gates pass but the strength of the tests themselves is uncertain.
    1 repo stars
  24. ▌
    Source Grounded Research 2 · jovanipink
    Research a question using current primary sources, preserving publisher URLs, dates, units, provenance, and uncertainty. Use for web investigations, fact checks, comparisons, or recommendations where current evidence and precise attribution matter.
    1 repo stars
  25. ▌
    Workflow Retrospective 2 · jovanipink bundle
    Review a completed or paused workflow using supplied artifacts and current task evidence to identify what helped, what failed, why, and which bounded improvement to test next. Invoke explicitly after meaningful work; do not mine private histories or automatically rewrite policy or skills.
    1 repo stars
  26. ▌
    Accessibility Review 2 · jovanipink
    Review web or application accessibility using WCAG 2.2 success criteria, semantic structure, keyboard behavior, assistive-technology needs, visual presentation, and user impact. Use for evidence-based findings without claiming conformance from incomplete testing.
    1 repo stars
  27. ▌
    Observability Design 2 · jovanipink
    Review or design observability for services and applications using logs, metrics, traces, alerts, and user-impact signals. Use when operators need to detect, explain, and respond to failures without confusing telemetry volume with operational understanding.
    1 repo stars
  28. ▌
    Change Impact Analysis 2 · jovanipink
    Analyze the blast radius of a proposed or completed change across callers, contracts, storage, jobs, clients, security, rollout, and operations. Use before review, merge, or release when downstream effects may be missed; do not substitute speculation for traced dependencies.
    1 repo stars
  29. ▌
    Authority Boundary Review 2 · jovanipink
    Review a system or migration to identify authoritative stores, exact-byte custody, projections, writers, readers, reconciliation paths, and ratified versus proposed contracts. Use for data architecture, migration, integration, and source-of-truth decisions.
    1 repo stars
  30. ▌
    Cross Stack Quality Gates 2 · jovanipink bundle
    Discover and run the repository's real validation gates across supported application, language, data, and infrastructure stacks without assuming a universal command. Use after changes, before review, or when asked whether a codebase passes its checks.
    1 repo stars
  31. ▌
    Decision Evidence Trace 2 · jovanipink bundle
    Maintain a bounded decision and evidence trail for a long-running task without exposing hidden reasoning, raw transcripts, secrets, or unrelated activity. Invoke explicitly when the user wants an auditable task log in chat or an authorized append-only file.
    1 repo stars
  32. ▌
    Requirements Synthesis 2 · jovanipink
    Synthesize interviews, documents, issues, observations, and constraints into traceable requirements. Use when multiple sources must become a decision-ready scope without turning proposals or preferences into ratified facts.
    1 repo stars
  33. ▌
    Agent Evaluation Design 2 · jovanipink bundle
    Design an evaluation contract for an AI agent, model-assisted workflow, or prompt-driven system using representative cases, baselines, configurations, graders, error classes, thresholds, cost, latency, human review, and limitations. Use when the decision depends on measured AI behavior across cases; use test-strategy for ordinary software coverage and test-quality-review for an existing test suite.
    1 repo stars
  34. ▌
    Respond To Code Review 2 · jovanipink
    Evaluate code review feedback against current code, tests, contracts, and authority before accepting, rejecting, or deferring it. Use when review comments contain claims or requested changes that require technical verification.
    1 repo stars
  35. ▌
    Kpi Outcome Measurement 2 · jovanipink
    Design or review outcome measurement with precise definitions, units, populations, baselines, targets, data authority, and decision use. Use when a program or product needs measures that distinguish activity, output, outcome, and impact.
    1 repo stars
  36. ▌
    Portable Skill Authoring 2 · jovanipink bundle
    Design or revise a portable Agent Skill with precise routing, invocation policy, focused references, provenance, security boundaries, evals, and generated client adapters. Use for cross-client SKILL.md catalog work; do not trigger for ordinary documentation or client-specific command files.
    1 repo stars
  37. ▌
    Implementation Planning 2 · jovanipink bundle
    Produce a decision-complete implementation plan grounded in repository and platform evidence. Use when a change needs concrete interfaces, ordered steps, tests, rollout controls, checkpoints, and stopping conditions before work begins.
    1 repo stars
  38. ▌
    Module Interface Design 2 · jovanipink
    Design or review a module boundary, vocabulary, interface, and hidden implementation so callers face a smaller and more stable contract. Use when code is coupled, concepts leak across layers, responsibilities are unclear, or a redesign needs concrete options before implementation.
    1 repo stars
  39. ▌
    Change Adoption Planning 2 · jovanipink
    Plan organizational or product change around affected people, behavior, capability, incentives, support, measurement, and feedback. Use when technical delivery alone will not produce the intended operating outcome.
    1 repo stars
  40. ▌
    Data Migration Readiness 2 · jovanipink
    Review a proposed data or schema migration for authority, compatibility, sequencing, reconciliation, rollback, and operational evidence. Use before a migration or cutover; do not execute or ratify the migration.
    1 repo stars
  41. ▌
    Functional Motion Review 2 · jovanipink bundle
    Review whether interface motion clarifies evidence, sequence, comparison, or reader actions. Use for animated editorial and data experiences; not for routine styling, implementing animation, or claiming engagement from visual polish.
    1 repo stars
  42. ▌
    Domain Vocabulary Modeling 2 · jovanipink
    Build a proposed domain vocabulary from current code, documents, and stakeholder language, including concepts, definitions, relationships, invariants, authorities, examples, and contradictions. Use when inconsistent terms are causing design or communication errors; do not treat the result as ratified without owner evidence.
    1 repo stars
  43. ▌
    Finish Development Branch 2 · jovanipink bundle
    Reconcile a development branch and present evidence-based options for pull request, merge, retention, or cleanup. Invoke explicitly when implementation is complete enough to decide the branch's next state without assuming push, merge, deletion, or abandonment authority.
    1 repo stars
  44. ▌
    Multi Agent Orchestration 2 · jovanipink bundle
    Coordinate authorized parallel agents on independent bounded tasks with explicit ownership, evidence contracts, cost awareness, and final reconciliation. Invoke explicitly when parallel work can reduce latency without creating edit collisions or delegating irreversible decisions.
    1 repo stars
  45. ▌
    Example Authority Policy 2 · jovanipink bundle
    Apply a fictional repository's local authority policy when reviewing example records. Use only inside this sanitized example to demonstrate private overlay placement.
    1 repo stars
  46. ▌
    Context Reliability Review 2 · jovanipink bundle
    Review the reliability of context assertions supplied to an AI system by tracing provenance, authority, freshness, effective and recorded time, permissions, conflicts, supersession, and revocation. Use when agent behavior depends on whether contextual claims are current and allowed; use authority-boundary-review for system-of-record architecture rather than assertion-level context.
    1 repo stars
  47. ▌
    Public Private Boundary Review 2 · jovanipink
    Review code, documentation, examples, articles, or release artifacts before public exposure to find secrets, internal identifiers, private operational details, proprietary material, and claims unsupported by public evidence. Use before open-sourcing or publishing work derived from mixed public and private contexts.
    1 repo stars
  48. ▌
    Go Engineering Profile 2 · jovanipink bundle
    Apply focused Go engineering judgment after repository gate discovery. Use for Go modules, packages, concurrency, APIs, tests, dependencies, compatibility, and build concerns; defer exact commands to repository evidence.
    1 repo stars
  49. ▌
    Acceptance Evidence Ledger 2 · jovanipink bundle
    Create or update an acceptance ledger for substantial work that needs explicit outcomes, current evidence, re-verification, and visible blockers or abandonments. Invoke explicitly when a user requests an inline or repository-owned completion contract; use focused testing, execution, or claim-verification skills for one-time requests.
    1 repo stars
  50. ▌
    Decision Governance Records 2 · jovanipink
    Create or review decision records that preserve context, options, evidence, ownership, status, consequences, and review triggers. Use when a proposal must be distinguished from a ratified, rejected, superseded, or unresolved decision.
    1 repo stars
  51. ▌
    Workshop Planning Synthesis 2 · jovanipink
    Plan a workshop around a concrete decision or learning outcome, then synthesize its evidence without manufacturing consensus. Use for agendas, facilitation structure, prework, participation, decisions, actions, and follow-up.
    1 repo stars
  52. ▌
    Application Security Review 2 · jovanipink
    Review application or service security against current threat evidence and verifiable control requirements. Use for read-only assessment of authentication, authorization, input handling, data protection, session, error, configuration, and abuse risks; do not use this skill to audit agent packages.
    1 repo stars
  53. ▌
    Production Incident Analysis 2 · jovanipink
    Analyze a production incident using timestamped evidence, system behavior, contributing conditions, response actions, and recovery. Use after an incident to establish what happened, why controls failed, and what learning or remediation is justified.
    1 repo stars
  54. ▌
    High Signal Technical Writing 2 · jovanipink bundle
    Edit technical prose for clarity, evidence density, specificity, rhythm, and audience fit while preserving meaning and repository voice. Use for completion reports, status updates, or documentation that sounds vague, repetitive, promotional, or machine-generic; do not use style heuristics as evidence of authorship.
    1 repo stars
  55. ▌
    Research To Publication Lifecycle 2 · jovanipink bundle
    Coordinate an explicitly requested source-to-publication learning lifecycle across research, evidence tracing, model or forecast evaluation, corrections, and retrospective findings. Invoke explicitly when the user wants traceable knowledge objects or a public-safe research index; do not use for a one-off search, ordinary summary, or automatic publication.
    1 repo stars
  56. ▌
    Operational Readiness Review 2 · jovanipink
    Review whether a service or application is operationally ready for release and sustained ownership. Use for read-only assessment of objectives, dependencies, monitoring, alerts, capacity, failure handling, incidents, runbooks, recovery, and support boundaries.
    1 repo stars
  57. ▌
    Iteration Postlaunch Learning 2 · jovanipink
    Plan and synthesize postlaunch learning from observed behavior, incidents, feedback, experiments, and outcome measures. Use after a release when the team must decide what to retain, change, investigate, or stop.
    1 repo stars
  58. ▌
    Design Rationale Investigation 2 · jovanipink
    Investigate why code, architecture, or an operational design exists by comparing direct historical evidence, current behavior, and competing hypotheses. Use for design history and rationale questions; do not infer intent from code shape alone or search unrelated private sources.
    1 repo stars
  59. ▌
    Merge Conflict Reconciliation 2 · jovanipink bundle
    Reconcile an active Git merge, rebase, or cherry-pick conflict by inspecting exact repository state, preserving both sides' intent, validating the result, and keeping abort available. Invoke explicitly for an identified conflicted worktree; staging, continuing, committing, and pushing require separate authority.
    1 repo stars
  60. ▌
    Python Engineering Profile 2 · jovanipink bundle
    Apply focused Python engineering judgment after repository gate discovery. Use for Python packages, typing, async behavior, tests, dependencies, compatibility, and builds; defer exact commands to repository evidence.
    1 repo stars
  61. ▌
    Source Output Conformance Audit 2 · jovanipink bundle
    Audit whether exact source identity and expected values survive parsing or extraction, validation, persistence, and readback using source-cited oracles and mutation-sensitive tests. Use for end-to-end source-to-output fidelity claims; use test-quality-review for test-suite quality and authority-boundary-review for ownership architecture alone.
    1 repo stars
  62. ▌
    Dependency Supply Chain Review 2 · jovanipink
    Review software dependencies and build supply-chain evidence for provenance, integrity, maintenance, vulnerability, and compromise risk. Use for a read-only assessment of manifests, lockfiles, registries, build inputs, CI actions, artifacts, and update policy.
    1 repo stars
  63. ▌
    Adobe Aem Engineering Profile 2 · jovanipink bundle
    Apply focused Adobe Experience Manager engineering judgment after repository gate discovery. Use for AEM as a Cloud Service or AEM 6.5 code, Sling and OSGi, content packages, Dispatcher, caching, tests, compatibility, and builds; preserve separate Cloud Manager authority.
    1 repo stars
  64. ▌
    Terraform Engineering Profile 2 · jovanipink bundle
    Apply focused Terraform engineering judgment after repository gate discovery. Use for modules, providers, state, plans, upgrades, compatibility, and infrastructure review; validation never implies apply authority.
    1 repo stars
  65. ▌
    API Contract Compatibility Review 2 · jovanipink
    Review API, event, schema, and client changes for backward, forward, and rollout compatibility. Use when producers and consumers may upgrade independently or when a change can alter behavior, shape, timing, errors, or semantics.
    1 repo stars
  66. ▌
    Performance Scalability Diagnosis 2 · jovanipink
    Diagnose latency, throughput, resource, contention, and scalability problems using measured evidence and competing hypotheses. Use when a system is slow, unstable under load, or approaching a capacity boundary; do not silently optimize code.
    1 repo stars
  67. ▌
    PHP Drupal Engineering Profile 2 · jovanipink bundle
    Apply focused PHP and Drupal engineering judgment after repository gate discovery. Use for Composer projects, Drupal modules or themes, entity and configuration APIs, caching, security, tests, compatibility, and builds; defer exact commands to repository evidence.
    1 repo stars
  68. ▌
    Agentic System Security Review 2 · jovanipink bundle
    Review an agentic system across agent identity, models, instructions, tools, memory, retrieval, delegation, protocols, guardrails, outputs, supply chain, cost, revocation, and emergency stopping. Use for a read-only threat and control assessment of model-mediated actions; use application-security-review for conventional application controls and skill-security-review for a skill package.
    1 repo stars
  69. ▌
    Google Adk Engineering Profile 2 · jovanipink bundle
    Review or design a Google Agent Development Kit system using exact framework, language, model, session, tool, evaluation, and deployment evidence. Use for human-facing ADK architecture and version discovery; combine it with the focused agent security, evaluation, context, retrieval, and operational skills instead of treating framework defaults as proof of safety or readiness.
    1 repo stars
  70. ▌
    Cross Capability Dependency Mapping 2 · jovanipink
    Map dependencies across products, teams, data, platforms, decisions, and operating capabilities. Use when delivery or outcomes depend on multiple owners and hidden sequencing, authority, or failure paths must be made explicit.
    1 repo stars
  71. ▌
    Stakeholder Technical Communication 2 · jovanipink bundle
    Translate technical evidence for a named stakeholder decision without overstating certainty, hiding risk, or exposing inappropriate detail. Use for executive summaries, review packets, status updates, decision briefs, and cross-functional explanations.
    1 repo stars
  72. ▌
    Value Attribution Evidence Maturity 2 · jovanipink
    Assess claimed value, benefit, savings, risk reduction, or outcome contribution against an explicit evidence-maturity model. Use when stakeholders need to distinguish observed results, estimates, attribution, contribution, and causal claims.
    1 repo stars
  73. ▌
    Java Spring Engineering Profile 2 · jovanipink bundle
    Apply focused Java and Spring engineering judgment after repository gate discovery. Use for JVM services, Spring Boot applications, concurrency, transactions, tests, dependencies, compatibility, and builds; honor repository wrappers and toolchains.
    1 repo stars
  74. ▌
    Data Authority Migration Ratification 2 · jovanipink
    Prepare a proposed data-authority and migration decision record covering owners, writers, readers, cutover, reconciliation, rollback, and acceptance. Use when decision owners need evidence to ratify or reject a migration contract; the skill cannot ratify it.
    1 repo stars
  75. ▌
    Csharp Dotnet Engineering Profile 2 · jovanipink bundle
    Apply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.
    1 repo stars
  76. ▌
    Swift Swiftui Engineering Profile 2 · jovanipink bundle
    Apply focused Swift and SwiftUI engineering judgment after repository gate discovery. Use for packages, applications, concurrency, UI state, tests, compatibility, and builds; require observed macOS evidence for Apple toolchain claims.
    1 repo stars
  77. ▌
    Agent Context State Memory Design 2 · jovanipink bundle
    Design or review how an agent separates prompt context, session events, scoped state, long-term memory, and artifacts. Use when identity, authority, freshness, retention, provenance, tenant isolation, poisoning, or deletion behavior could change what an agent knows or does; use context-reliability-review for a supplied context packet rather than the hosting architecture.
    1 repo stars
  78. ▌
    Agent Tool Action Boundary Review 2 · jovanipink bundle
    Review the boundary between an agent and its registered tools or actions, including identity, permissions, schemas, argument controls, network reach, confirmation, idempotency, replay protection, rollback, and audit evidence. Use before an agent can read sensitive data or cause an external effect; use application-security-review for broader application controls.
    1 repo stars
  79. ▌
    Postgresql SQL Engineering Profile 2 · jovanipink bundle
    Apply focused PostgreSQL and SQL engineering judgment after repository gate discovery. Use for schemas, queries, transactions, migrations, indexing, compatibility, and database test concerns; never mutate shared data merely to validate.
    1 repo stars
  80. ▌
    Retrieval Grounding Quality Review 2 · jovanipink bundle
    Review whether an agent retrieval and grounding system selects authorized, current, relevant evidence and produces claims that the evidence actually supports. Use for corpus authority, tenant filtering, retrieval metrics, citation support, abstention, poisoning, and injection; use source-grounded-research for a human research task and source-output-conformance-audit for deterministic source-to-output transformation.
    1 repo stars
  81. ▌
    Salesforce Apex Engineering Profile 2 · jovanipink bundle
    Apply focused Salesforce, Apex, and Lightning Web Components engineering judgment after repository gate discovery. Use for metadata projects, packages, governor limits, data access, tests, compatibility, and deployment readiness; preserve separate live-org authority.
    1 repo stars
  82. ▌
    Agent Protocol Interoperability Review 2 · jovanipink bundle
    Review interoperability across agent, tool, and service protocols using exact versions, discovery records, schemas, identity, authorization, delegation, streaming, errors, retries, idempotency, cancellation, and trust zones. Use for A2A, MCP, or another agent-facing protocol boundary; use api-contract-compatibility-review for an ordinary API change without agent delegation semantics.
    1 repo stars
  83. ▌
    Typescript Javascript Engineering Profile 2 · jovanipink bundle
    Apply focused TypeScript and JavaScript engineering judgment after repository gate discovery. Use for Node or browser packages, type safety, async behavior, tests, dependencies, compatibility, and builds; honor the repository package manager and scripts.
    1 repo stars
  84. ▌
    Workflow Retrospective · jovanipink bundle
    Review a completed or paused workflow using supplied artifacts and current task evidence to identify what helped, what failed, why, and which bounded improvement to test next. Invoke explicitly after meaningful work; do not mine private histories or automatically rewrite policy or skills.
    1 repo stars
  85. ▌
    Agent Evaluation Design · jovanipink bundle
    Design an evaluation contract for an AI agent, model-assisted workflow, or prompt-driven system using representative cases, baselines, configurations, graders, error classes, thresholds, cost, latency, human review, and limitations. Use when the decision depends on measured AI behavior across cases; use test-strategy for ordinary software coverage and test-quality-review for an existing test suite.
    1 repo stars
  86. ▌
    Decision Evidence Trace · jovanipink bundle
    Maintain a bounded decision and evidence trail for a long-running task without exposing hidden reasoning, raw transcripts, secrets, or unrelated activity. Invoke explicitly when the user wants an auditable task log in chat or an authorized append-only file.
    1 repo stars
  87. ▌
    Implementation Planning · jovanipink bundle
    Produce a decision-complete implementation plan grounded in repository and platform evidence. Use when a change needs concrete interfaces, ordered steps, tests, rollout controls, checkpoints, and stopping conditions before work begins.
    1 repo stars
  88. ▌
    Kpi Outcome Measurement · jovanipink bundle
    Design or review outcome measurement with precise definitions, units, populations, baselines, targets, data authority, and decision use. Use when a program or product needs measures that distinguish activity, output, outcome, and impact.
    1 repo stars
  89. ▌
    Module Interface Design · jovanipink bundle
    Design or review a module boundary, vocabulary, interface, and hidden implementation so callers face a smaller and more stable contract. Use when code is coupled, concepts leak across layers, responsibilities are unclear, or a redesign needs concrete options before implementation.
    1 repo stars
  90. ▌
    Skill Import Provenance · jovanipink bundle
    Review provenance before transferring Jovani-owned skill material between authorized repositories or distributions. Invoke explicitly for an owned-source transfer or a decision about whether proposed external skill material must be rejected; third-party skill catalogs are never implementation sources.
    1 repo stars
  91. ▌
    Change Adoption Planning · jovanipink bundle
    Plan organizational or product change around affected people, behavior, capability, incentives, support, measurement, and feedback. Use when technical delivery alone will not produce the intended operating outcome.
    1 repo stars
  92. ▌
    Data Migration Readiness · jovanipink bundle
    Review a proposed data or schema migration for authority, compatibility, sequencing, reconciliation, rollback, and operational evidence. Use before a migration or cutover; do not execute or ratify the migration.
    1 repo stars
  93. ▌
    Functional Motion Review · jovanipink bundle
    Review whether interface motion clarifies evidence, sequence, comparison, or reader actions. Use for animated editorial and data experiences; not for routine styling, implementing animation, or claiming engagement from visual polish.
    1 repo stars
  94. ▌
    Portable Skill Authoring · jovanipink bundle
    Design or revise a portable Agent Skill with precise routing, invocation policy, focused references, provenance, security boundaries, evals, and generated client adapters. Use for cross-client SKILL.md catalog work; do not trigger for ordinary documentation or client-specific command files.
    1 repo stars
  95. ▌
    Source Grounded Research · jovanipink bundle
    Research a question using current primary sources, preserving publisher URLs, dates, units, provenance, and uncertainty. Use for web investigations, fact checks, comparisons, or recommendations where current evidence and precise attribution matter.
    1 repo stars
  96. ▌
    Authority Boundary Review · jovanipink bundle
    Review a system or migration to identify authoritative stores, exact-byte custody, projections, writers, readers, reconciliation paths, and ratified versus proposed contracts. Use for data architecture, migration, integration, and source-of-truth decisions.
    1 repo stars
  97. ▌
    Cross Stack Quality Gates · jovanipink bundle
    Discover and run the repository's real validation gates across supported application, language, data, and infrastructure stacks without assuming a universal command. Use after changes, before review, or when asked whether a codebase passes its checks.
    1 repo stars
  98. ▌
    Finish Development Branch · jovanipink bundle
    Reconcile a development branch and present evidence-based options for pull request, merge, retention, or cleanup. Invoke explicitly when implementation is complete enough to decide the branch's next state without assuming push, merge, deletion, or abandonment authority.
    1 repo stars
  99. ▌
    Multi Agent Orchestration · jovanipink bundle
    Coordinate authorized parallel agents on independent bounded tasks with explicit ownership, evidence contracts, cost awareness, and final reconciliation. Invoke explicitly when parallel work can reduce latency without creating edit collisions or delegating irreversible decisions.
    1 repo stars
  100. ▌
    Acceptance Evidence Ledger · jovanipink bundle
    Create or update an acceptance ledger for substantial work that needs explicit outcomes, current evidence, re-verification, and visible blockers or abandonments. Invoke explicitly when a user requests an inline or repository-owned completion contract; use focused testing, execution, or claim-verification skills for one-time requests.
    1 repo stars