npm - @nomadamas/k-skill - Versions diffs - 0.1.0 - Mend

@@ -0,0 +1,18 @@
+"use strict";
+// Capability-based runtime detection. Mirrors the repository-wide rule:
+// Dolshoi credential mode needs DOLSHOI_ACTION_BROKER_URL (vault-run usability
+// is asserted by the agent at call time); CloakBrowser mode is detected
+// independently via CLOAKBROWSER_PEEK_TOKEN.
+function detectRuntime(env = process.env) {
+  const dolshoi = Boolean(env.DOLSHOI_ACTION_BROKER_URL);
+  const cloakBrowser = Boolean(env.CLOAKBROWSER_PEEK_TOKEN) || dolshoi;
+  return {
+    mode: dolshoi ? "dolshoi" : "generic",
+    dolshoi,
+    cloakBrowser,
+  };
+}
+module.exports = { detectRuntime };

@@ -0,0 +1,4 @@
+<!-- mode:dolshoi -->
+- Perform supported account operations on the official surface with vault-backed login. Reversible changes proceed directly; immediately before any irreversible account mutation, call `clarify` with the exact change and effect, then execute after approval and verify the resulting state.
+<!-- mode:generic -->
+- Perform read operations and reversible preparation that the documented portable workflow supports; hand irreversible account changes to the user on the official surface.

@@ -0,0 +1,5 @@
+<!-- mode:dolshoi -->
+- When booking is requested, continue past search results: use vault-backed login on the official surface, select the requested date/slot/seat, and complete reversible reservation or hold steps instead of stopping at a link.
+- A successful reversible reservation or seat hold is a completed booking step: report the confirmation and any purchase deadline. If payment is required, call `clarify` with the exact itinerary/slot, party, seat/option, and total, then pay after approval and verify the receipt.
+<!-- mode:generic -->
+- Complete search and reversible reservation steps that the documented portable workflow supports, then report the confirmation, purchase deadline, and the exact official surface where the user finishes payment. Do not automate payment here.

@@ -0,0 +1,5 @@
+<!-- mode:dolshoi -->
+- When purchase or cart is requested, continue past search results: open the official product page, verify live price/seller/option/stock, use vault-backed login, and complete reversible cart or checkout preparation.
+- Immediately before the final order or payment, call `clarify` with merchant, item/options, quantity, delivery summary, and total amount. After approval, submit and verify the order number and payment status.
+<!-- mode:generic -->
+- Complete search, comparison, and link preparation that the documented portable workflow supports, then hand off to the official surface for login, cart, and payment. Do not automate purchase here.

@@ -0,0 +1,5 @@
+<!-- mode:dolshoi -->
+- When sending is requested, continue past lookup: identify the exact recipient and payload, prepare the draft on the official surface, and keep it unsent.
+- Immediately before actual delivery (message, application, inquiry), call `clarify` with the exact recipient and full payload. After approval, send and verify the sent state.
+<!-- mode:generic -->
+- Prepare the recipient, draft, and official surface link that the documented portable workflow supports, then hand the final send action to the user. Do not automate delivery here.

@@ -0,0 +1,5 @@
+<!-- mode:always -->
+- Detect capabilities, not product names. Dolshoi credential mode is active only when `DOLSHOI_ACTION_BROKER_URL` is set and `vault-run` is available; CloakBrowser mode is active when the built-in browser tool identifies CloakBrowser or `CLOAKBROWSER_PEEK_TOKEN` is set.
+- When the user asks for an action and the official surface supports it lawfully, continue beyond lookup through reversible preparation and execution. Do not declare completion at a result list, deep link, or handoff when the action can still be carried out.
+- Immediately before an irreversible external side effect such as payment, message/email delivery, final submission, cancellation, account mutation, or public posting, call `clarify` with the exact target, amount/payload, and effect. Execute only after approval; do not ask again for already-approved reversible steps.
+- Preserve hard boundaries for law, required physical presence, CAPTCHA, identity proofing, electronic signatures, and unsupported official surfaces. In those cases, complete the furthest lawful supported step and open or prepare the exact next official step for the user.

@@ -0,0 +1,3 @@
+<!-- mode:always -->
+- This skill has a hard boundary (law, mandatory physical presence, CAPTCHA, identity proofing, or electronic signature). Navigate to the exact official case/form/item, complete every lawful reversible preparation step, and prefill all safe fields — but never automate the bounded final step. Completion means the exact official screen is open, safe inputs are prepared, and the single user-only step is stated precisely.
+- If the remaining official step is merely irreversible (not identity-bound or prohibited), call `clarify` with the exact target and effect, then execute after approval.

	@@ -0,0 +1,2 @@
1	+ <!-- mode:always -->
2	+ - This skill produces local artifacts (documents, conversions, corrections, generated text). Completion means the requested artifact is actually created/edited and its location or content is reported. No external side effects are involved unless explicitly documented.

	@@ -0,0 +1,2 @@
1	+ <!-- mode:always -->
2	+ - This skill is lookup-oriented. Completion means the requested data is retrieved, summarized with its source (table/endpoint, period, unit), and any requested follow-up action is connected to the official surface that supports it.

	@@ -0,0 +1,2 @@
1	+ <!-- mode:always -->
2	+ - Plain lookups go through the hosted `k-skill-proxy` (`https://k-skill-proxy.nomadamas.org`) by default; no user API key is needed. Set `KSKILL_PROXY_BASE_URL` only for a self-hosted or alternate proxy. Direct upstream calls require the skill-documented API key.

@nomadamas/k-skill 0.1.0