Import & Export

Workspace File Format

Every skrptiq workspace is a directory of plain files — markdown for nodes, YAML for configuration. This means your work is human-readable, version-controllable with git, and portable.

Node Files

Each node is a markdown file with YAML frontmatter, stored in a subdirectory matching its type:

my-skrpt/
├── skills/text-summarisation.md
├── prompts/summarise-text.md
├── workflows/pr-review-pipeline.md
├── services/anthropic-claude.md
└── ...

A node file looks like this:

---
type: skill
id: text-summarisation
title: Text Summarisation
description: "Condenses long-form text into key points"
tags: [Production, Tested]
connections:
  - target: anthropic-claude
    type: runs_on
  - target: meeting-protocol
    type: references
---
## Capability
Reduces lengthy documents, transcripts, or articles to concise summaries.

## When to Use
- Meeting notes need sharing with absent colleagues
- Research articles need quick-scan versions

The frontmatter captures the node’s identity, tags, and outgoing connections. The markdown body is the node’s content — the same text you edit in the node editor.

Supporting Files

File	Purpose
`skrptiq.yaml`	Workspace manifest — name, dependencies, metadata. See skrptiq.yaml reference.
`tags.yaml`	Tag definitions (name and colour) used by nodes in this workspace.
`.skrptiq/local.yaml`	Local-only state (node positions, UI preferences). Gitignored — not shared.
`.gitignore`	Excludes `.skrptiq/` from version control.

JSON Export

Click Export in the toolbar to download a snapshot of your entire graph.

The export produces a file called skrptiq-export.json with the following structure:

{
  "version": "0.1.0",
  "exportedAt": "2026-03-03T...",
  "nodes": [...],
  "edges": [...]
}

What’s included:

All nodes in the current graph (skills, prompts, workflows, sources, documents, assets, services)
All connections (edges) between nodes
Node content, descriptions, and metadata

What’s excluded:

Tags — these are local organisational data and are not exported
Layout positions — the graph is re-laid out on import

Dependencies

You can add external skrptiq graphs as dependencies via the Repos View. This is useful for pulling in shared prompt libraries, service configurations, or workflow templates maintained by other people.

Dependencies are cloned from git and their nodes appear read-only in your graph
Use the Fork action to copy dependency objects into your local workspace for editing
Forked nodes become fully editable and are included in your exports

Dependencies are declared in the workspace manifest:

dependencies:
  company-core:
    source: "https://github.com/acme/core-skills.git"
    version: "^2.0.0"
    objects: "*"

See the skrptiq.yaml reference for the full dependency syntax.