nuskills 0.1.0__tar.gz

nuskills-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+.venv/
+__pycache__/
+*.egg-info/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/

nuskills-0.1.0/LICENSE.md

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2025 Gor Arakelyan
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied. See the License for the specific language governing
+   permissions and limitations under the License.

nuskills-0.1.0/PKG-INFO

@@ -0,0 +1,151 @@
+Metadata-Version: 2.5
+Name: nuskills
+Version: 0.1.0
+Summary: Tested prompt pieces and agent skills for Nu and nuspace.
+Project-URL: Repository, https://github.com/nustackdev/nuskills
+Author-email: Gor Arakelyan <gorarkln@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE.md
+Keywords: agents,llm,nu,nuspace,nustack,prompt,skills
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# nuskills
+
+Prompt text about Nu and nuspace, in one place, tested against the current code.
+
+- **nuagent** loads pieces into its system prompt.
+- **Outside agents** (Claude Code, Codex) get skills built from the same pieces.
+- Every fenced Python block in the corpus is built against the latest nucore, nustd and nuspace, so a piece cannot go stale without a red test.
+
+## Layout
+
+```
+src/nuskills/
+  __init__.py      loader: pieces(), load(), read(), __version__
+  corpus/
+    nu/            the kernel: thesis, crashcourse, composition, ...
+    nustd/         fabrics: kv, mem, ui, ...
+    nuspace/       the space model, ops, snippets, drawing a cell
+  skills.py        which pieces each built skill carries, in order
+  headers/         per skill SKILL.md frontmatter and a few lines of when-to-use
+  build.py         assembles skills/ from headers + pieces
+skills/            built skills, committed, never edited by hand
+.claude-plugin/    plugin.json + marketplace.json: the repo is a Claude Code plugin
+tests/             the block harness, the loader tests, the skills checks
+```
+
+## Using it from Python
+
+```python fragment
+import nuskills
+
+nuskills.pieces("nu")              # ["nu/crashcourse", ...]
+nuskills.read("nu/crashcourse")    # markdown, frontmatter stripped
+nuskills.load("nu/crashcourse")    # Piece(id, title, summary, body)
+```
+
+Each consumer picks its pieces and decides their order. nuagent pins `nuskills` and assembles its system prompt from them, adding its own agent-specific text (role, protocol, finish) and the generated parts (the `nu.inspect` catalogue, the app surface). The pieces are package data, so `importlib.resources.files("nuskills") / "corpus" / "nu" / "crashcourse.md"` reaches the raw file too; the loader is the supported way.
+
+## Skills
+
+A skill is a header plus an ordered list of pieces, defined in `src/nuskills/skills.py`:
+
+| Skill | For |
+| --- | --- |
+| `nu` | building Nu programs and apps (kernel + nustd fabrics, kv, service, ui) |
+| `nuspace` | programming a running nuspace (cell progs, ops, brackets, state, drawing, snippets) |
+
+Each one is built in Claude Code's progressive disclosure layout. `SKILL.md` holds the header, a table of the reference files with each piece's summary, and the pieces every task needs (`inline`). The rest (`reference`) are files next to it, read only when the task needs one, so they cost no context until then. A piece's mention of another piece (`nustd/ui-refs`) becomes a link to wherever it landed.
+
+```
+skills/<name>/
+  SKILL.md
+  reference/<group>/<piece>.md
+```
+
+The skills carry no catalogue. They tell the agent to render the API with `nu.inspect` in its own environment, so a skill is right for whatever version is installed.
+
+Rebuild after editing a piece, a header or `skills.py`, and commit the result. `tests/test_skills.py` fails while `skills/` is out of date.
+
+```bash
+uv run python -m nuskills.build            # write skills/
+uv run python -m nuskills.build --check    # exit 1 if skills/ is out of date
+```
+
+### Installing in Claude Code
+
+The repo is a plugin marketplace (`nustack`) holding one plugin (`nuskills`):
+
+```bash
+claude plugin marketplace add nustackdev/nuskills
+claude plugin install nuskills@nustack
+```
+
+Inside a session, `/plugin marketplace add nustackdev/nuskills` then `/plugin install nuskills@nustack` do the same. The skills show up as `/nuskills:nu` and `/nuskills:nuspace`, and Claude also loads them on its own when a task matches their description. To try a local checkout without installing: `claude --plugin-dir path/to/nuskills`. Validate after editing the manifests: `claude plugin validate .`.
+
+## Writing a piece
+
+A piece is one markdown file, `corpus/<group>/<name>.md`, its id is `<group>/<name>`. Keep it small enough to be picked on its own. Store only text that can't be generated: the catalogue (`nu.inspect`) and an app's surface are built at prompt time, never written here.
+
+Optional frontmatter, `title` and `summary` only:
+
+```text
+---
+title: Crash course
+summary: The ten things you write in every Nu program.
+---
+```
+
+### Fences
+
+The info string on the opening fence says what the harness does with the block.
+
+| Fence | Meaning | Checked by |
+| --- | --- | --- |
+| ```` ```python ```` | a whole program | loaded, `out` called, `nu.validate(nu.compile(term))` |
+| ```` ```python run ```` | a whole program that finishes quickly in memory | the above, then evaluated with `nu.arun` (10s cap) |
+| ```` ```python fragment ```` | a few lines, not a program | Python `compile()` only |
+| anything else (`text`, `bash`, ...) | prose | skipped |
+
+Any other word after `python` fails the test, so a typo can't turn a program into prose.
+
+A whole program is a module with an entry point `out`, loaded by `nu.prog`'s own loader (the one nuspace uses for a cell):
+
+- `out` is a function returning a Nu term, or a term itself.
+- `out` takes only what its signature asks for, by name.
+- In `nu/` and `nustd/` pieces nothing is offered: write `def out():`.
+- In `nuspace/` pieces the block is a cell program. It is stored as a cell on a plane in an in-memory space and loaded the way the kernel loads it. `out` may ask for `plane` and `cell`, the ids as plain `str`. `CellState` and `PlaneState` slots land under that cell and plane. Store access needs its own bracket, as in a real cell (`ops.atomic_state(...)`, `ops.snapshot(...)`). A `run` block runs inside the cell's `ops.Here` frame against that space. There is no browser session, so a block that draws should not be marked `run`.
+- A string literal in a block that contains `def out(` is another program's source (eg the cell an `ops.add_cell` adds) and is built the same way, under the same group's rules.
+
+Mark `run` only on programs that finish and touch nothing outside memory. A program that subscribes, waits or serves stays unmarked: built and validated, not run.
+
+## Checking a piece
+
+```bash
+uv sync                                  # once: Python 3.10 .venv with the sibling repos editable
+uv run pytest -k nuspace/model           # every block in one piece
+uv run pytest -k "nu/crashcourse:42"     # one block: piece and the fence's line
+uv run pytest                            # everything
+uv run ruff check
+```
+
+Each block is its own test, id `<piece>:<line>`, the line of its opening fence, so a failure points at the exact block. The dev env installs `../nu`, `../nu/pkgs/nustd[all]`, `../nuspace` and `../nuverse/pkgs/nuverse` editable, so it tests against main.
+
+## CI
+
+`.github/workflows/test.yml` runs ruff, the skills check and pytest against two stacks: **main** (nu, nuspace and nuverse checked out next to this repo, as `[tool.uv.sources]` expects) and **released** (the latest `nustd[all]`, `nuspace`, `nuverse` from PyPI). It runs on push and PR, nightly, by hand, and on a `repository_dispatch` (`nu-release`, `nuspace-release`, `nuverse-release`) a sibling release fires; the header of the workflow has the step a sibling adds.
+
+## Versions
+
+`nuskills` versions on its own, not in step with nu. CI tests the corpus against both current main and the latest released stack, so a version only says what changed in the text. `.claude-plugin/plugin.json` carries the same version as `pyproject.toml` (a test checks it), so installed plugins update when it moves.
+
+Release: bump `version` in `pyproject.toml` and `.claude-plugin/plugin.json`, rename the CHANGELOG's `Unreleased` heading to the version + date, commit and push, then `git tag nuskills@X.Y.Z && git push origin nuskills@X.Y.Z`. `.github/workflows/publish.yml` publishes to PyPI (trusted publisher) and cuts a GitHub Release.
+

nuskills-0.1.0/README.md

@@ -0,0 +1,132 @@
+# nuskills
+
+Prompt text about Nu and nuspace, in one place, tested against the current code.
+
+- **nuagent** loads pieces into its system prompt.
+- **Outside agents** (Claude Code, Codex) get skills built from the same pieces.
+- Every fenced Python block in the corpus is built against the latest nucore, nustd and nuspace, so a piece cannot go stale without a red test.
+
+## Layout
+
+```
+src/nuskills/
+  __init__.py      loader: pieces(), load(), read(), __version__
+  corpus/
+    nu/            the kernel: thesis, crashcourse, composition, ...
+    nustd/         fabrics: kv, mem, ui, ...
+    nuspace/       the space model, ops, snippets, drawing a cell
+  skills.py        which pieces each built skill carries, in order
+  headers/         per skill SKILL.md frontmatter and a few lines of when-to-use
+  build.py         assembles skills/ from headers + pieces
+skills/            built skills, committed, never edited by hand
+.claude-plugin/    plugin.json + marketplace.json: the repo is a Claude Code plugin
+tests/             the block harness, the loader tests, the skills checks
+```
+
+## Using it from Python
+
+```python fragment
+import nuskills
+
+nuskills.pieces("nu")              # ["nu/crashcourse", ...]
+nuskills.read("nu/crashcourse")    # markdown, frontmatter stripped
+nuskills.load("nu/crashcourse")    # Piece(id, title, summary, body)
+```
+
+Each consumer picks its pieces and decides their order. nuagent pins `nuskills` and assembles its system prompt from them, adding its own agent-specific text (role, protocol, finish) and the generated parts (the `nu.inspect` catalogue, the app surface). The pieces are package data, so `importlib.resources.files("nuskills") / "corpus" / "nu" / "crashcourse.md"` reaches the raw file too; the loader is the supported way.
+
+## Skills
+
+A skill is a header plus an ordered list of pieces, defined in `src/nuskills/skills.py`:
+
+| Skill | For |
+| --- | --- |
+| `nu` | building Nu programs and apps (kernel + nustd fabrics, kv, service, ui) |
+| `nuspace` | programming a running nuspace (cell progs, ops, brackets, state, drawing, snippets) |
+
+Each one is built in Claude Code's progressive disclosure layout. `SKILL.md` holds the header, a table of the reference files with each piece's summary, and the pieces every task needs (`inline`). The rest (`reference`) are files next to it, read only when the task needs one, so they cost no context until then. A piece's mention of another piece (`nustd/ui-refs`) becomes a link to wherever it landed.
+
+```
+skills/<name>/
+  SKILL.md
+  reference/<group>/<piece>.md
+```
+
+The skills carry no catalogue. They tell the agent to render the API with `nu.inspect` in its own environment, so a skill is right for whatever version is installed.
+
+Rebuild after editing a piece, a header or `skills.py`, and commit the result. `tests/test_skills.py` fails while `skills/` is out of date.
+
+```bash
+uv run python -m nuskills.build            # write skills/
+uv run python -m nuskills.build --check    # exit 1 if skills/ is out of date
+```
+
+### Installing in Claude Code
+
+The repo is a plugin marketplace (`nustack`) holding one plugin (`nuskills`):
+
+```bash
+claude plugin marketplace add nustackdev/nuskills
+claude plugin install nuskills@nustack
+```
+
+Inside a session, `/plugin marketplace add nustackdev/nuskills` then `/plugin install nuskills@nustack` do the same. The skills show up as `/nuskills:nu` and `/nuskills:nuspace`, and Claude also loads them on its own when a task matches their description. To try a local checkout without installing: `claude --plugin-dir path/to/nuskills`. Validate after editing the manifests: `claude plugin validate .`.
+
+## Writing a piece
+
+A piece is one markdown file, `corpus/<group>/<name>.md`, its id is `<group>/<name>`. Keep it small enough to be picked on its own. Store only text that can't be generated: the catalogue (`nu.inspect`) and an app's surface are built at prompt time, never written here.
+
+Optional frontmatter, `title` and `summary` only:
+
+```text
+---
+title: Crash course
+summary: The ten things you write in every Nu program.
+---
+```
+
+### Fences
+
+The info string on the opening fence says what the harness does with the block.
+
+| Fence | Meaning | Checked by |
+| --- | --- | --- |
+| ```` ```python ```` | a whole program | loaded, `out` called, `nu.validate(nu.compile(term))` |
+| ```` ```python run ```` | a whole program that finishes quickly in memory | the above, then evaluated with `nu.arun` (10s cap) |
+| ```` ```python fragment ```` | a few lines, not a program | Python `compile()` only |
+| anything else (`text`, `bash`, ...) | prose | skipped |
+
+Any other word after `python` fails the test, so a typo can't turn a program into prose.
+
+A whole program is a module with an entry point `out`, loaded by `nu.prog`'s own loader (the one nuspace uses for a cell):
+
+- `out` is a function returning a Nu term, or a term itself.
+- `out` takes only what its signature asks for, by name.
+- In `nu/` and `nustd/` pieces nothing is offered: write `def out():`.
+- In `nuspace/` pieces the block is a cell program. It is stored as a cell on a plane in an in-memory space and loaded the way the kernel loads it. `out` may ask for `plane` and `cell`, the ids as plain `str`. `CellState` and `PlaneState` slots land under that cell and plane. Store access needs its own bracket, as in a real cell (`ops.atomic_state(...)`, `ops.snapshot(...)`). A `run` block runs inside the cell's `ops.Here` frame against that space. There is no browser session, so a block that draws should not be marked `run`.
+- A string literal in a block that contains `def out(` is another program's source (eg the cell an `ops.add_cell` adds) and is built the same way, under the same group's rules.
+
+Mark `run` only on programs that finish and touch nothing outside memory. A program that subscribes, waits or serves stays unmarked: built and validated, not run.
+
+## Checking a piece
+
+```bash
+uv sync                                  # once: Python 3.10 .venv with the sibling repos editable
+uv run pytest -k nuspace/model           # every block in one piece
+uv run pytest -k "nu/crashcourse:42"     # one block: piece and the fence's line
+uv run pytest                            # everything
+uv run ruff check
+```
+
+Each block is its own test, id `<piece>:<line>`, the line of its opening fence, so a failure points at the exact block. The dev env installs `../nu`, `../nu/pkgs/nustd[all]`, `../nuspace` and `../nuverse/pkgs/nuverse` editable, so it tests against main.
+
+## CI
+
+`.github/workflows/test.yml` runs ruff, the skills check and pytest against two stacks: **main** (nu, nuspace and nuverse checked out next to this repo, as `[tool.uv.sources]` expects) and **released** (the latest `nustd[all]`, `nuspace`, `nuverse` from PyPI). It runs on push and PR, nightly, by hand, and on a `repository_dispatch` (`nu-release`, `nuspace-release`, `nuverse-release`) a sibling release fires; the header of the workflow has the step a sibling adds.
+
+## Versions
+
+`nuskills` versions on its own, not in step with nu. CI tests the corpus against both current main and the latest released stack, so a version only says what changed in the text. `.claude-plugin/plugin.json` carries the same version as `pyproject.toml` (a test checks it), so installed plugins update when it moves.
+
+Release: bump `version` in `pyproject.toml` and `.claude-plugin/plugin.json`, rename the CHANGELOG's `Unreleased` heading to the version + date, commit and push, then `git tag nuskills@X.Y.Z && git push origin nuskills@X.Y.Z`. `.github/workflows/publish.yml` publishes to PyPI (trusted publisher) and cuts a GitHub Release.
+

nuskills-0.1.0/pyproject.toml

@@ -0,0 +1,151 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+# Text only: the corpus of prompt pieces about Nu and nuspace, plus a tiny
+# loader. Every fenced block in it is built against the current nucore, nustd
+# and nuspace by tests/test_blocks.py. Versioned on its own, not in step with nu.
+[project]
+name = "nuskills"
+version = "0.1.0"
+description = "Tested prompt pieces and agent skills for Nu and nuspace."
+readme = "README.md"
+license = "Apache-2.0"
+authors = [{ name = "Gor Arakelyan", email = "gorarkln@gmail.com" }]
+requires-python = ">=3.10"
+# No runtime dependencies: the package ships text. Consumers read pieces
+# through `nuskills.load` / `importlib.resources`.
+dependencies = []
+keywords = [
+    "nu",
+    "nustack",
+    "nuspace",
+    "prompt",
+    "skills",
+    "agents",
+    "llm",
+]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+]
+
+[project.urls]
+Repository = "https://github.com/nustackdev/nuskills"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/nuskills"]
+
+[tool.hatch.build.targets.sdist]
+only-include = [
+    "src/nuskills",
+    "README.md",
+]
+
+# =============================================================================
+# Dev env: the corpus is tested against the stack as it is on main
+# =============================================================================
+# Sibling checkouts, editable, the same wiring the nuverse workspace uses.
+# `[tool.uv.sources]` never reaches published metadata.
+[tool.uv.sources]
+nucore = { path = "../nu", editable = true }
+nustd = { path = "../nu/pkgs/nustd", editable = true }
+nuspace = { path = "../nuspace", editable = true }
+nuspace-ui = { path = "../nuspace/pkgs/ts/nuspace-ui", editable = true }
+nuverse = { path = "../nuverse/pkgs/nuverse", editable = true }
+
+[tool.uv]
+default-groups = ["dev"]
+
+[dependency-groups]
+dev = [
+    # What the blocks are built against: the kernel, every fabric, nuspace,
+    # and nuverse's std snippets a nuspace piece may name.
+    "nucore",
+    "nustd[all]",
+    "nuspace",
+    "nuverse",
+    "ruff>=0.8.0",
+    "pytest>=7.0.0",
+    "pytest-asyncio>=1.3.0",
+    "pytest-timeout>=2.1.0",
+]
+
+[tool.pytest.ini_options]
+testpaths = [
+    "tests",
+]
+# `tests/_lib` is the only test directory on sys.path, and `_support` the only
+# thing in it.
+pythonpath = [
+    "tests/_lib",
+]
+python_files = ["test_*.py"]
+python_classes = ["Test*"]
+python_functions = ["test_*"]
+addopts = ["-ra", "--strict-markers", "--strict-config", "--import-mode=importlib"]
+asyncio_mode = "auto"
+xfail_strict = true
+timeout = 60
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+src = [
+    "src",
+]
+# Corpus blocks live in markdown and are checked by the harness, not ruff.
+extend-exclude = [".venv", "build", "dist", "*.egg-info", "_archive"]
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "W",
+    "F",
+    "I",
+    "B",
+    "C4",
+    "UP",
+    "N",
+    "YTT",
+    "S",
+    "T20",
+    "D",
+    "ANN",
+    "TC",
+    "RUF",
+    "PTH",
+]
+ignore = [
+    "E501",
+    "D105",
+    "D107",
+]
+
+[tool.ruff.lint.pydocstyle]
+convention = "google"
+
+[tool.ruff.lint.per-file-ignores]
+"**/tests/**/*.py" = [
+    "S101", "S108", "T20", "D", "E711", "E712", "ANN", "N806",
+]
+
+[tool.ruff.lint.isort]
+known-first-party = [
+    "nuskills",
+    "nuspace",
+    "nuverse",
+    "nu",
+    "nustd",
+]
+force-single-line = false
+lines-after-imports = 2
+
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"