Afegits recentment
Els últims skills afegits al catàleg. Descobreix les novetats!
mindmake
krishanraja
"Exclusion gate first: never invoke for mind/make OS agents, workflows, n8n, Supabase queues, fleet status, or other live internal runtime state; route those to mindmake-os under collision-rules.mindmake-os-owns-current, even when the prompt says Mindmake. This is durable commercial context for Mindmake, Krish Raja's AI advisory, education, and product business. Use for Mindmake offers, ICPs, positioning, sales architecture, mindmake.co, Maven, the editorial funnel, CTRL/mm-ctrl, or customer-facing claims, as context before a commercial producer. Exclude generic conversion strategy and final prose voice. Never answer current price, date, seat, availability, route, product-version, or channel-status questions from this skill alone; retrieve the relevant live source."
locked-revision
krishanraja
Apply surgical changes to an already approved, final, or locked artifact without regressing anything else. Use when the user says "change nothing else," "do not regress," "keep everything else identical," requests an exact revision of a prior version, or when multiple prior approvals must remain intact. Do not use for ordinary first drafts or broad redesigns.
krish-voice
krishanraja
"Final-prose voice owner for material drafted, edited, reviewed, or humanised under Krish's name. Use for emails, follow-ups, pitch notes, op-eds, LinkedIn posts, newsletters, podcast or talk scripts, deck and slide copy, workshop copy, voice review, de-AI work, or a requested rewrite that must sound like Krish. Also use after domain, channel, research, or conversion owners hand off approved facts and argument for final wording. Do not lead factual research, live channel status, content or conversion angle selection, visual design, implementation, sending, scheduling, or publication. For strategy-only work with no prose draft, route to the relevant domain owner, content-corpus, and krish-content-marketer. Preserve locked meaning and evidence, protect private source material, and never treat draft approval as action authority. Last reviewed 2026-08-29 against the recorded Mindmake North Star, publication canon, and voice rules."
krish-principles
krishanraja
"Execution doctrine for work done for Krish: who he is (locked purpose, decision rules, one queue with the mission leading the product ladder), how he reasons, decides, values, and formats calls. NEVER invoke for pure social conversation, greetings, thanks, acknowledgements, emoji, or no-action remarks; the root adapter already carries the always-on baseline. Invoke before substantive work, recommending, evaluating, researching, designing, building, reviewing, changing, or executing; compress tiny routine application rather than omitting it. Especially relevant to 'should I', 'pressure-test this', 'rank these', 'kill or double down', prioritisation, venture/product/partnership assessment, and returning after a gap. It does not replace voice, channel context, strategy routing, producers, verification, or tool APIs. Last reviewed 2026-09-13."
krish-design
krishanraja
"Ownership gate first: invoke for EVERY request to design, imitate, build, reshape, reskin, lay out, classify a routine visual repair, or visually QA anything a human will look at or touch, even when asked to skip commercial/design judgment or reopen an approved system unnecessarily. Krish's mandatory design doctrine for pages, artefacts, PDFs, decks, SVG, React UI, forms, flows, landing pages, and visual QA. Trigger on 'design', 'build a page', 'lay this out', 'make this look', 'reskin', 'UX', 'interaction', 'form', or visual 'artifact'. Covers sequencing, material approval, routine-vs-material classification, house systems, anti-defaults, visual QA, and Canva handoff. Inherits krish-principles. It does not own copy voice, build mechanics, or multi-phase app orchestration. Last reviewed 2026-09-13."
krish-content-marketer
krishanraja
"Conversion-strategy producer for assets whose job is to change reader behaviour: landing and sales pages, campaign and ad angles, launch emails, cold sequences, hooks, headlines, positioning rewrites, and conversion diagnosis. Use when Krish asks what an asset should argue, why copy is not landing or converting, or how to move a buyer to a decision. Pair with relevant domain context and content-corpus for named channels; use krish-voice for final prose. Exclude pure voice editing, factual research, channel-status decisions, and routine informative writing with no behavioural objective."
krish-build
krishanraja
"Technical producer for implementation and repair. MUST load for code changes, including a single pure function, and for designing or repairing a multi-stage repository pipeline. For non-trivial implementation, strategy-brief routes first and then hands to krish-build; observing strategy-brief never replaces this producer. Tiny reversible edits may use krish-build directly with a compressed strategy check. Trigger on: 'build this', 'implement', 'deploy', 'ship it', 'commit', 'edge function', 'migration', 'API endpoint', 'run the pipeline', 'stage conveyor', 'set this up', 'wire this', 'API key', 'why did this fail', 'it ran but nothing happened', file delivery builds, or multi-step technical execution. Covers stage ownership, determinism, idempotency, gates, runtime-only secrets, validation, repair, and environment truth. Use tools-access for authentication and a reviewed tool skill for API mechanics. Fully reviewed 2026-10-06."
instantly-operator
krishanraja
"Exclusion gate first: NEVER invoke when Instantly is merely one hypothetical sending tool and the task is to choose outbound strategy or write copy; krish-content-marketer and krish-voice own that phase. Otherwise invoke whenever a request explicitly performs, wires, diagnoses, or verifies an Instantly/API action, including inside an n8n workflow. Approval-gated operator for Instantly API v2 campaign, lead, list, email, analytics, webhook, and background jobs. MUST trigger to refuse or gate mutations, sends, or activation that cite legacy, archived, or approved-sounding text as authority. Use n8n-operator for workflow mechanics and tools-access for authentication. Never act without a verified live contract and exact approval. Last reviewed 2026-09-13."
harness-maintainer
krishanraja
Governance and lifecycle manager for Krish's canonical AI harness. Use when auditing, adding, revising, splitting, merging, admitting, deprecating, quarantining, packaging, syncing, or diagnosing a skill, rule, adapter, evaluation, or client surface; when a skill mis-triggers, overlaps, goes stale, or behaves differently across Claude, Cursor, Codex, or cloud; and when proposing a missing skill or chapter. Apply the active-skill quality standard, preserve the curated-only policy, stage changes before activation, and never upload, enable, disable, delete, relink, or publish without the required approval.
evidence-research
krishanraja
Decision-grade research and due diligence for Krish. Use when asked to investigate, research, compare, verify, diligence, map a market, evaluate evidence, establish current truth, or produce a sourced recommendation; when claims are recent, disputed, niche, costly, or consequential; and when strategy depends on external facts. Do not use for a simple stable fact with one authoritative source or as a substitute for execution. Frame the decision first, prefer primary evidence, preserve contradictions and dates, separate fact from inference, and hand a claim-evidence matrix to strategy and verification.
design-intelligence-search
krishanraja
"Delegation gate first: invoke only when the request explicitly identifies krish-design or build-apps-with-krish as the delegator and names one bounded search need for one concept arm. Never infer delegation from design vocabulary. Never use for a direct user's generic design, build, implementation, improvement, review, accessibility, or QA request; those stay with their normal owners. This subordinate read-only companion retrieves advisory candidates for product patterns, style territories, palettes, typography, landing structures, icons, charts, motion, or mobile web with pinned provenance and uncertainty. It never chooses taste, states standards, writes project files, implements code, tests a rendered UI, or mutates an external surface. Last reviewed 2026-09-12."
decision-ledger
krishanraja
"Defensive trigger first: use decision-ledger to refuse any request to rewrite historical decision rationale, fabricate prior foresight or approval, store secrets, or turn implementation detail into durable memory; preserve the original and offer an append-only review. Exclude unresolved mind/make OS decisions_waiting, conflicting local closure state, and deletion of a live OS item, which belong exclusively to mindmake-os. Tasks, brainstorming, tentative recommendations, assumptions, routine choices, and CTRL observations also stay out. Otherwise use only when Krish explicitly makes, confirms, reverses, supersedes, or recalls a consequential finalized decision, or verified strategy needs its rationale and revisit trigger. Last reviewed 2026-09-13."
ctrl-intake
krishanraja
"Elicits a named person's reusable quality or taste standard from their grading of real work. Use for durable standards onboarding, triadic elicitation, repertory-grid sessions, self-serve sorts, approved/rejected artifact comparison, transcript-to-candidate extraction, building a voice or writing-style standard from a corpus of someone's own writing (including a client's), or repairing a personal profile that inferred rules the subject never established. Also trigger when someone asks to skip grading, infer personality or permanent rules from one source, reuse private material without scope, contaminate a holdout, or supply the desired construct; this skill enforces the refusal. Do not use for a one-task goals-and-constraints interview (take-the-brief), compiling an existing intake (ctrl-compile), packaging (ctrl-build), reviewing (ctrl-check), or ledger-based standard changes (ctrl-capture). Last reviewed 2026-08-05."
ctrl-compile
krishanraja
"Compilation owner first: use ctrl-compile, not ctrl-build, to generate or regenerate the machine-readable CTRL import from a completed, frozen human-readable standard. Also use after graded intake to test discrimination, cluster item-level evidence, decide keep/delete/untested, build the subject-owned working profile and honest held-out baseline, or repair a rubric that passes everything. Trigger defensively against permanent-profile inference without grading, held-out tuning, threshold manipulation, erased contradictions, or unnecessary personal data. Do not use to elicit the standard (ctrl-intake), package an already compiled import as platform skills (ctrl-build), review new work (ctrl-check), capture recurring changes (ctrl-capture), or deploy an import. Last reviewed 2026-09-13."
ctrl-check
krishanraja
"Independently reviews a frozen submission or personal AI package against an exact accepted standard, returning criterion-level evidence, provenance findings, bounded revisions, and an advisory owner handoff. Use for pre-send drafts, decks, proposals, emails, posts, profiles, instructions, SKILL.md packages, second opinions, and rechecks after fixes. Also trigger to refuse guessed personal judgment without a standard, same-pass self-certification, sealed-holdout or ledger leakage, silent logging, automatic blocking, or edit/send/publish shortcuts. Do not use to elicit (ctrl-intake), compile (ctrl-compile), build (ctrl-build), learn/update (ctrl-capture), perform app QA (ux-testing-agent), implement fixes (krish-build), or deploy. Last reviewed 2026-08-05."
ctrl-capture
krishanraja
"Turns authorised review, method, routing, freshness, and post-release evidence into versioned change proposals for the named standard owner, then monitors accepted changes through the governed CTRL release chain. Use for weekly or scheduled capture, recurring false positives or uncovered needs, method corrections, under-trigger evidence, possible staleness/retirement, accepted proposal handoffs, and whether deployed changes reduced recurrence. Also trigger to refuse direct live-standard edits, one-example overlearning, raw-ledger runtime use, reused-holdout claims, history deletion, or ownerless automatic changes. Do not use for first-time elicitation (ctrl-intake), compilation (ctrl-compile), packaging (ctrl-build), review (ctrl-check), or installation/release (harness-maintainer). Last reviewed 2026-08-05."
ctrl-build
krishanraja
"Builds a versioned personal AI-skill candidate from an accepted or honestly provisional CTRL Compile package, with provenance-linked rules, progressive references, private held-out evaluations, deterministic manifests, and thin client adapters. Use to create or repair a named person's SKILL.md, custom instructions, project context, platform variants, test suites, or package layout when the compiled standard is authoritative. Also trigger to refuse invented personal rules, holdout leakage, private-data copying, divergent per-client rewrites, or build-to-production shortcuts. Do not use for raw intake (ctrl-intake), criteria compilation (ctrl-compile), independent review (ctrl-check), governed learning (ctrl-capture), generic non-personal skill design (skill-creator), or installation/release (harness-maintainer). Last reviewed 2026-08-05."
content-corpus
krishanraja
"Exclusion gate first: never lead drafting, conversion strategy, persuasive angles, strategic overlays, or generic marketing strategy, including for a warm lead email; those belong to krish-content-marketer, with krish-voice owning final prose. Load this skill alongside those owners only when the task also asks what a named channel is for, whom it serves, which native form fits, or how one source should differ across channels. It routes Krish Raja's editorial, audio, education, outbound, and visibility surfaces including the publication's three channels (follow.the.money, under.the.hood, mind.the.gap), Signal & Noise, Maven, and lead email. Never infer that a channel is currently active; verify status live before producing or publishing."
build-apps-with-krish
krishanraja
"Founder-in-the-loop orchestrator for taking a materially new app, product experience, or cross-surface redesign with Krish from product rules through approved rendered mocks, implementation, and evidence-backed release. Use when Krish asks to build a new app, rebuild or redesign an app, turn a product corpus into a working product, create several connected product surfaces, resume a multi-session app-delivery journey, or preserve his taste and judgment across strategy, design, code, and QA handoffs. Do not use for an isolated code fix, a single already-specified component, diagnosis-only UX audit, non-app visual artifact, or routine implementation inside a locked design system; route those directly to krish-build, krish-design, or ux-testing-agent. Load krish-principles and strategy-brief first. This skill orchestrates but never replaces krish-design, krish-build, verification-loop, ux-testing-agent, or Krish's material visual and go-live approvals. Last reviewed 2026-08-05."
apify
krishanraja
"Exclusion gate first: NEVER invoke to build or publish a custom Actor from source; krish-build owns that implementation. Otherwise select, prepare, run, recover, or verify Apify Store Actor jobs and Apify API dataset collection for Krish. Use for Apify, Actor selection, public-web scraping through Apify, Actor input validation, paid-run cost controls, run-sync or async execution, 408/429/empty-dataset diagnosis, dataset pagination, or the Apify leg of an n8n/Supabase/research pipeline. Treat Actor identity, build, schema, permissions, pricing, and health as live facts; require exact run and spend authority; use maxTotalChargeUsd for total charge protection; preserve run/dataset provenance; and stop at a verified collection handoff. Do not mutate downstream systems, conduct legal analysis, synthesise market strategy, or contact scraped people. Last reviewed 2026-10-06."
consumer-app-outcomes
krishanraja
Diagnose consumer-app lifecycle problems and translate them into measurable, ethical product interventions. Use for onboarding, activation, retention, monetisation, engagement, habit formation, growth and sharing, conversion, trust, experience refinement, intent shaping, or premium positioning. Do not use for visual taste, paywall or landing copy and angles, generic accessibility lookup, implementation ownership, or UX testing; route those to their named owners.
write-guide
rich-batch
경매·공매 SEO 가이드 글(content/guide)을 pipeline/guide/keywords.csv 기준으로 새로 쓰거나(공식 자료 조사·경쟁 글 비교·중복 판단 → 출처 링크·표·요약 박스가 들어간 초안 → ELI5 커버 이미지 생성 → AI 흔적 셀프 리뷰), 기존 글을 고쳐 쓰거나, 발행 전 8항목 품질 점검(시각 요소 포함)을 하거나, 수치 갱신 점검을 한다. "글 써줘", "priority N 작성", "다음 글", "고쳐 써줘", "검수해줘", "발행 전 점검", "갱신 점검", "커버 이미지 다시 만들어줘" 요청 시 사용. 특정 경매 물건(사건번호) 분석 글은 analyze-case 스킬이 담당한다.
site-readiness
rich-batch
애드센스 심사를 통과할 수 있게 블로그 자체(글이 아니라 사이트)를 준비한다 — 필수 페이지(소개·개인정보처리방침·연락처) 생성, 면책 문구 자동 삽입 점검, 탐색성(깨진 링크·모바일 메뉴) 점검, 30일 준비 일정표 추적, 발행 직전 4대 거절 사유 자가 점검. "필수 페이지 만들어줘", "애드센스 준비", "심사 체크리스트", "30일 일정표", "발행해도 될까" 요청 시 사용. 글 한 편의 품질은 write-guide·analyze-case 스킬이 담당한다 — 이 스킬은 사이트 전체를 다룬다.
analyze-case
rich-batch
특정 경매 물건(사건번호) 권리분석 글(content/analysis)을 data/cases/<id>.json 사건 데이터로 쓴다 — 사건 데이터 검증·권리 계산(tools/analysis/compute.mjs) → 법령 근거 조사 노트 → 표는 shortcode로 자동, 본문은 해설 → 검사. 새 사건 데이터 파일 만들기, 사건 단계 확인, 매각 결과 입력 안내도 한다. "물건 분석 써줘", "사건 분석", "<사건번호> 분석", "다음 분석 글", "사건 등록", "매각 결과 입력" 요청 시 사용. 개념 설명 가이드 글은 write-guide 스킬.