jupi-co/jupi-skills (log-decision)

Record a decision the user has ALREADY made into Jupi (the team's decision platform) as a finalized, searchable entry — the title, the chosen path, and the rationale. Use whenever a choice gets settled and the user wants it captured: "log this decision", "record that we're going with X", a validated trade-off, a meeting outcome, an ADR-style note, or the conclusion of a discussion you just had together. This spans any ideation or strategy work, not just product — a feature direction, but equally a GTM call, a pricing choice, a hire, an org or ops change. When the work is still exploratory (brainstorming, weighing options), wait — only offer to log once it has landed on a direction, never mid-stream. At that closing moment, lean toward offering it: decisions captured in the flow of work stay searchable later; the ones "written up afterward" evaporate. This finalizes the decision in one step, so use it only for calls that are actually made, not open questions (for those, use submit-decision).

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/jupi-co/jupi-skills

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

7 critical findings reported by cisco-skill-scanner, agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.