# neklvl.dev

Technical writing, agent skills, and Codex plugin work for humans and agents.

Canonical URL: https://neklvl.dev/

## Site model

neklvl.dev publishes technical writing and tooling notes for agent work. The public surface emphasizes stable metadata, clear summaries, and Markdown-readable material for agents that need to inspect the site without visual interpretation.

Public skill and plugin source material is currently summarized, not mirrored in full, unless it is already visible on the site.

## Skills directory

### Agent skills

Reusable instructions for agent workflows. This page will index individual skills once the private source is wired into the site build.

- Kind: skill
- Status: source-private
- Source: private source
- Tags: agents, instructions, workflows

### Design direction

Local design and product context that keeps future site work aligned with the neklvl.dev identity.

- Kind: skill
- Status: planned
- Source: neklvl.dev
- Tags: design, documentation, site

## Plugins directory

### Codex plugins

Plugin bundles for Codex workflows. This directory will become a curated index of capabilities, install notes, and source metadata.

- Kind: plugin
- Status: source-private
- Source: private source
- Tags: codex, plugins, agents

### Skill registry bridge

A future bridge between private source material and public, structured directory pages for humans and agents.

- Kind: plugin
- Status: planned
- Source: neklvl.dev
- Tags: registry, metadata, publishing

## Articles

### Article: Field notes for neklvl.dev

A short note on the shape of neklvl.dev: readable to humans, structured for agents, and quiet by default.

- Type: article
- Source: neklvl
- Published: 2026-06-05
- Canonical URL: https://neklvl.dev/articles/field-notes/

`neklvl.dev` is a structured home before it is a feed.

The site is meant to hold articles, agent skills, and Codex plugins without asking a human persona to carry the identity. The durable objects are the notes, the source metadata, and the directories that make the material inspectable.

## Reading model

Human readers should be able to scan by title, summary, date, source, and tags. Agent readers should find the same facts in predictable headings and visible metadata. The design treats those needs as the same discipline.

## Directory model

Skills and plugins start as curated lists. Later, they can become generated indexes sourced from private materials, with stable summaries and metadata for each entry.

## Design model

The interface should stay quiet: white surface, dark ink, precise rules, and a small signature mark. The site should avoid template polish and terminal costume. It should feel useful before it feels expressive.