NKSKILLS / VERSIONED SKILL WORKFLOWS

Skills with a source. Workflows with a purpose.

Combine original and public skills into a workflow with a defined output, version, and traceable sources. Start with codebase onboarding for engineers.

Built for Codex + Claude CodeTechnical release 1.1.0
NK / 001COMPOSITION LOCK
● TECHNICAL RELEASE

codebase
onboarding

@1.1.0
01codebase-onboarding-c4original workflow
02html-docs-standardoriginal docs
03hallmarkpinned upstream
OUTPUTProduct journey · C1/C2 · File evidence
01 TECHNICAL PRODUCT RELEASE02 SUPPORTED HOSTSREAD THE RELEASE RECORD ↗
01 / THE IDEA

A product layer over individual skills

Individual skills bring capability. A Solution Skill owns the outcome.

NKSkills selects public skills, records their commits and licenses, and composes them with original workflows. Each combo has its own manifest, prerequisites, output, and version.

UPSTREAM SKILL

Selected capability

Public source, license, commit, and local changes are tracked.

SOLUTION SKILL

Outcome-driven workflow

Sequence, prerequisites, components, and verification criteria are versioned.

Explore the full catalog ↗

03 / TRY IT

Start with one prompt.

Select your host and language, review the prompt, then copy. Install the skill from GitHub and prepare CodeGraph before running it.

STARTER PROMPTcodebase-onboarding@1.1.0
Choose your host
Prompt language

The prompt checks prerequisites first. The AI must stop before installing tools, creating an index, or editing files if setup is incomplete.

04 / IN PRACTICE

From repository to reviewable understanding.

The workflow checks prerequisites before analysis and makes uncertainty visible.

01 / PREPARE

Install and verify

Build from GitHub, verify the digest, and prepare codegraph, rtk, and a valid root index.

02 / TRACE

Follow one journey

Follow an entry point through real logic and data; distinguish evidence from inference.

03 / REVIEW

Review the output

Review diagrams, citations, and open questions before relying on the output.

NKSkills codebase onboarding workflow
From traceable components through a versioned Solution Skill to a codebase map that needs human review.
  1. Hallmark + original skills
  2. codebase-onboarding@1.1.0
  3. Codex or Claude Code
  4. Cited journey and C1/C2 views

05 / CATALOG

A collection with provenance.

Public skills are selected for a purpose, with versions and licenses tracked. An upstream change becomes a review candidate; an existing release does not change automatically.

Browse the catalog ↗
UPSTREAM / DESIGNhallmarkIn codebase onboarding
UPSTREAM / DIAGRAMSdiagram-designIn problem presentation candidate
UPSTREAM / AUTHORINGfrontend-design + copywritingUsed to build this site
+See every source and commit↗

06 / FAQ

Good to know.

Which hosts are supported?

Codex and Claude Code. Each has its own setup guide for codebase-onboarding.

Do upstream updates change a Solution Skill automatically?

No. We track sources, review new versions, then decide whether to issue a new Solution Skill release.

Can I use it on any project?

Version 1.1.0 has build and install checks, but behavior quality across repositories is not broadly verified. Review its output before making decisions.

How do I install the skill?

Build from GitHub source, verify the digest with the technical guide, then install in Codex or Claude Code. A direct-download archive is not published yet.

Will the prompt change my code?

The prompt asks for findings in chat first and approval before external access or artifact writes. If prerequisites are missing, the AI must stop before installing tools, indexing, or editing files.

NKSKILLS / CODEBASE ONBOARDING

Understand the system before you change it.

Copy the starter prompt ↗Explore solution ↗