# Rakenne 0.3.0 — Fork Skills and Remix with Attribution

> 0.3.0 adds one-click skill forking, lineage and "Based on…" attribution, the ability to publish skills publicly, plus version and changelog in the library.

Author: map[name:Rakenne team]
Published: 2026-02-13

URL: https://rakenne.app/learn/releases/rakenne-0-3-0/index.md


We're pleased to announce **Rakenne 0.3.0**. The focus is **skill forking** — you can now take any skill (system or your organization's), fork it into a new Skill Workshop project, adapt it, and publish your variant with full attribution to the original. You can also **publish skills publicly** so they are visible and shareable beyond your organization.

## Fork skills in one click

**Fork** lets you build on existing work instead of starting from scratch. In the skill library, open any skill's detail view and click **Fork**. You get:

- **New Workshop project** — A Skill Workshop project is created with the skill files copied into `output/{slug}/`, ready to edit. You can choose a custom slug (default: `{original-slug}-custom`) and pick which version to fork (latest or a specific release).
- **Fork metadata** — A `fork-origin.json` file is stored alongside the skill in the workspace so that when you publish, lineage is recorded automatically — no extra steps.
- **"Based on…" attribution** — Published forked skills show "Based on {original skill} v{version}" in the library and in the detail view, with a link back to the original when it still exists. Library cards display a **Forked** badge so you can see at a glance which skills are remixes.

Forking uses the same access rules as installing: you can fork system skills and any skill from your own tenant. Cross-tenant forking is not yet supported.

## Version and changelog in the library

- **Latest version** — Skill detail now shows the current version label (e.g. "v1.2") next to the title.
- **Changelog** — When a skill has release notes, a **Changelog** button opens a drawer with the version and notes so you can see what changed before installing or forking.
- **Version selector when forking** — The fork dialog lets you choose which version to fork (default: latest), so you can base your variant on a specific release.

## Lineage through publish

When you publish a forked skill from the Workshop, the backend reads `fork-origin.json` and sets **forked_from_package_id** and **forked_from_version** on the skill package. Attribution is preserved across fork → edit → publish without any extra input. If the original skill is later deleted, forked skills remain; the UI shows "Based on a skill that is no longer available" where the link would have been.

## Publish skills publicly

You can now publish skills as **public** so they are visible and shareable beyond your organization. When publishing from the Workshop, choose the visibility you want (private or public). Public skills can be discovered and installed by others; private skills stay within your tenant. Your organization's public slug is used for stable, shareable references to your published skills.


---

Thank you for using Rakenne. Try forking a skill from the [Skill Library](/learn/tutorials/) and publishing your variant — we'd love to hear how you're remixing and sharing workflows. Feedback is always welcome.

— The Rakenne team


---

Back to [Releases](https://rakenne.app/learn/releases/index.md)