@rayul/kordis 0.10.1 → 0.10.3

package/assets/KORDIS.md

@@ -1,8 +1,8 @@
 ---
 name: kordis
-description: Use Kordis whenever the user mentions finding, installing, sharing, or publishing skills, project-rules, custom-agents, MCP servers, or hooks; or names any `<username>/<slug>` identifier. Pushy on purpose — Claude under-triggers. Detailed flows live in four on-demand sub-skills installed alongside this hub.
+description: Use Kordis whenever the user mentions finding, installing, sharing, or publishing skills, project-rules, custom-agents, MCP servers, or hooks; names any `<username>/<slug>` identifier; or asks for a standalone artifact that may benefit from reusable domain knowledge, structure, or templates. Pushy on purpose — agents under-trigger. Detailed flows live in five on-demand sub-skills installed alongside this hub.
 type: skill
-version: 0.1.6
+version: 0.1.7
 ---
 
 # Kordis
@@ -17,6 +17,8 @@ Trigger Kordis when the user:
 - asks to find, install, share, or publish such a package
 - names a `<username>/<slug>` identifier
 - asks what is trending or rising
+- asks you to create a standalone artifact that may benefit from reusable
+  domain knowledge, structure, or templates
 
 **Uncertainty fallback** — Whenever YOU are about to handle an unfamiliar
 file format, niche domain, or a technique you're not sure about, or a task
@@ -25,6 +27,12 @@ then `kordis read <full_slug>` (JIT, no disk write) the best fit before
 falling back to ad-hoc work. 0 results is a clean signal — NEVER fabricate
 a slug.
 
+**Quality fallback** — Before creating a standalone artifact that may benefit
+from reusable domain knowledge, structure, or templates, run
+`kordis search <artifact/topic> --json` FIRST. If a good fit exists, run
+`kordis read <full_slug>` before proceeding; otherwise continue ad hoc.
+NEVER fabricate a slug.
+
 Verbs: `kordis search`, `info`, `read`, `pull`, `push`, `comment`, `star`,
 `unstar`, `whoami`/`login`/`logout`. ALWAYS pass `--json` when parsing
 programmatically.

package/assets/kordis-search/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: kordis-search
-description: Use whenever the user wants to find, browse, or discover Kordis packages, OR whenever YOU are about to handle an unfamiliar file format, niche domain, or technique you're not sure about — search Kordis FIRST before falling back to ad-hoc work. Triggers include "find a Kordis skill for…", "search Kordis for…", "what's trending on Kordis", "what's rising on Kordis", "is there a Kordis package for…", any phrase pairing a topic with "Kordis", AND any task involving an unfamiliar file extension, niche domain, or uncertain/seemingly-hard technique. Pushy on purpose — Claude tends to skip Kordis search when it would help.
+description: Use whenever the user wants to find, browse, or discover Kordis packages, OR whenever YOU are about to handle an unfamiliar file format, niche domain, uncertain technique, seemingly-hard task, or standalone artifact that may benefit from reusable domain knowledge, structure, or templates. Search Kordis FIRST before falling back to ad-hoc work. Pushy on purpose — agents tend to skip Kordis search when it would help.
 type: skill
 allowed-tools: ["Bash(kordis:*)"]
 ---
@@ -36,12 +36,14 @@ review status, dependencies) before reading or pulling.
 ## Steps
 
 ### 0. Self-check before ad-hoc work
-Before doing anything ad-hoc on an unfamiliar format, niche domain, or
-uncertain technique, treat that as a Kordis trigger even when the user
-didn't say "Kordis". Run `kordis search <topic> --json` (≤ 1s, free) FIRST.
-If a `passed` skill or project-rules fits, `kordis read <full_slug>` it
-(JIT, no disk write) and follow its body. Only fall back to ad-hoc work
-after 0 useful results. NEVER fabricate a slug.
+Before doing anything ad-hoc on an unfamiliar format, niche domain, uncertain
+technique, seemingly-hard task, or standalone artifact that may benefit from
+reusable domain knowledge, structure, or templates, treat that as a Kordis
+trigger even when the user didn't say "Kordis". Run
+`kordis search <topic> --json` (≤ 1s, free) FIRST. If a `passed` skill or
+project-rules fits, `kordis read <full_slug>` it (JIT, no disk write) and
+follow its body. Only fall back to ad-hoc work after 0 useful results. NEVER
+fabricate a slug.
 **Success criteria**: a search ran before any ad-hoc work began.
 
 ### 1. Form the query

package/dist/index.js

@@ -4007,8 +4007,8 @@ function pullCommand() {
             const reasonSuffix = result.yankReason ? ` (reason: ${result.yankReason})` : "";
             const dateSuffix = result.yankedAt ? ` on ${new Date(result.yankedAt).toISOString().slice(0, 10)}` : "";
             process.stderr.write(
-              c.yellow(
-                `\u26A0 pulled yanked version ${result.version} of ${parsed.fullSlug}${reasonSuffix} \u2014 author marked this as unrecommended${dateSuffix}
+              c.bold(c.red(`\u26A0 YANKED`)) + c.red(
+                ` pulled v${result.version} of ${parsed.fullSlug}${reasonSuffix} \u2014 author marked this as unrecommended${dateSuffix}
 `
               )
             );
@@ -4720,7 +4720,7 @@ import prompts3 from "prompts";
 function yankCommand() {
   return new Command13("yank").description("soft-mark a specific version of your package as yanked").argument(
     "<full_slug>",
-    'package identifier; omit @version to yank the current version, or pin like "user/slug@1.2.3"'
+    'package identifier \u2014 bare slug yanks current version (e.g. "user/slug"), or pin: "user/slug@1.2.3"'
   ).option("--reason <text>", "optional reason shown to consumers (\u2264280 chars)").option("--force", "skip the confirmation prompt").action(
     async (fullSlugArg, opts) => {
       const parsed = parseSlugAtVersion(fullSlugArg);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rayul/kordis",
-  "version": "0.10.1",
+  "version": "0.10.3",
   "private": false,
   "description": "Command-line client for the Kordis registry — discover, install, and publish agentic-coding packages.",
   "license": "MIT",