RSS Reader using AT Protocol
rssbase.io
feed
atom
rss
reader
atproto
social
add tangled skill
Romain Gautier
(Jul 4, 2026, 10:39 AM +0200)
c630c92b
a8a0de86
+619
+83
.agents/skills/tangled/README.md
+83
.agents/skills/tangled/README.md
···
1
+
# Tangled Agent Skill
2
+
3
+
A platform-neutral Agent Skill for working with [Tangled.org](https://tangled.org/), the decentralized Git code hosting and collaboration platform built on AT Protocol.
4
+
5
+
This skill teaches Agent Skills-compatible AI coding agents how to use Tangled for repository hosting, Git operations, issues, pull requests, CI/CD workflows, webhooks, and AT Protocol-related troubleshooting.
6
+
7
+
## What this skill covers
8
+
9
+
- Tangled Git clone / push / pull / migration / mirroring workflows
10
+
- GitHub-to-Tangled concept and command mapping
11
+
- Tangled CLI usage patterns (`tang`, `tng`, `tangled`)
12
+
- Issue and pull request workflows
13
+
- SSH key and authentication troubleshooting
14
+
- AT Protocol basics: handles, DIDs, PDS, AppView, knots
15
+
- Spindles CI/CD workflows
16
+
- Tangled webhooks
17
+
18
+
## What this skill does not include
19
+
20
+
- No MCP dependency
21
+
- No embedded credentials or API keys
22
+
- No private SSH keys
23
+
- No executable scripts
24
+
25
+
It is intentionally written as Markdown-only skill documentation so it can be reused across Agent Skills-compatible and other skill-aware agent environments.
26
+
27
+
## Structure
28
+
29
+
```text
30
+
tangled/
31
+
├── SKILL.md
32
+
└── references/
33
+
├── atproto-troubleshooting.md
34
+
├── cli.md
35
+
├── git-ops.md
36
+
├── github-mapping.md
37
+
├── issues-prs.md
38
+
└── knots-spindles-webhooks.md
39
+
```
40
+
41
+
## Installation
42
+
43
+
Copy the `tangled/` directory into a supported skills directory.
44
+
45
+
For global skill-aware agent environments:
46
+
47
+
```bash
48
+
mkdir -p ~/.agents/skills
49
+
cp -R tangled ~/.agents/skills/tangled
50
+
```
51
+
52
+
For project-local usage:
53
+
54
+
```bash
55
+
mkdir -p .agents/skills
56
+
cp -R tangled .agents/skills/tangled
57
+
```
58
+
59
+
Then start a new agent session so the skill metadata can be discovered.
60
+
61
+
## Usage examples
62
+
63
+
Ask your agent things like:
64
+
65
+
- "Clone this Tangled repo."
66
+
- "Push this project to Tangled."
67
+
- "Mirror this GitHub repo to Tangled."
68
+
- "Create a Tangled issue for this bug."
69
+
- "Open a Tangled pull request from this branch."
70
+
- "Set up a Spindle workflow."
71
+
- "Why is Tangled SSH push failing?"
72
+
73
+
## Primary references
74
+
75
+
- Tangled: https://tangled.org/
76
+
- Tangled docs: https://docs.tangled.org/
77
+
- Quick start: https://docs.tangled.org/quick-start-guide
78
+
- Webhooks: https://docs.tangled.org/webhooks
79
+
- `tang` CLI: https://github.com/onevcat/tang
80
+
81
+
## License
82
+
83
+
MIT, unless a future maintainer chooses a different license file for this repository.
+109
.agents/skills/tangled/SKILL.md
+109
.agents/skills/tangled/SKILL.md
···
1
+
---
2
+
name: tangled
3
+
description: Works with Tangled.org, the decentralized Git code hosting and collaboration platform built on AT Protocol. Use when the user mentions Tangled, tangled.org, knots, spindles, AT Protocol Git hosting, Tangled repositories, Tangled issues, Tangled pull requests, Tangled CI/CD, migrating or mirroring GitHub/GitLab repos to Tangled, or controlling Tangled with git/CLI commands. Does not require MCP.
4
+
---
5
+
6
+
# Tangled
7
+
8
+
Use this skill for Tangled.org repository work: creating, cloning, pushing, pulling, mirroring, migrating, managing issues/PRs, configuring SSH keys, and setting up Tangled CI/CD/webhooks.
9
+
10
+
Tangled is not GitHub with a different domain. It is decentralized Git hosting built around AT Protocol identity, appviews, and repository hosting servers called knots. Prefer standard `git` for code transfer and a Tangled CLI for higher-level objects like issues and pull requests.
11
+
12
+
## First decisions
13
+
14
+
1. **Need only clone/push/pull/mirror?** Use standard Git commands. Read `references/git-ops.md`.
15
+
2. **Need repo creation, SSH keys, issues, or PRs?** Use a Tangled CLI if available. Read `references/cli.md` and `references/issues-prs.md`.
16
+
3. **Coming from GitHub/GitLab?** Read `references/github-mapping.md` and `references/git-ops.md`.
17
+
4. **Need CI/CD or webhook automation?** Read `references/knots-spindles-webhooks.md`.
18
+
5. **Authentication/identity is confusing?** Read `references/atproto-troubleshooting.md`.
19
+
20
+
## Safety and verification rules
21
+
22
+
- Before running commands that write to a repo or account, inspect the current repository and remotes with `git remote -v`, `git status`, and, if needed, the Tangled CLI status/context command.
23
+
- Do not assume a Tangled CLI is installed. Check with `command -v tang`, `command -v tng`, and/or `command -v tangled`.
24
+
- Do not install community CLIs globally without the user's approval. If a CLI is missing, explain the options and ask before installing.
25
+
- Treat Tangled CLIs as community tools unless the source proves otherwise. Prefer official Tangled docs for Git/SSH/Spindle/Webhook behavior.
26
+
- Never expose app passwords, PDS credentials, SSH private keys, tokens, or DID-linked account secrets in chat, logs, commits, or skill files.
27
+
- If asked to migrate from GitHub/GitLab, state that Tangled's official docs describe Git history migration via remotes; issues and pull requests are not automatically migrated by the basic Git workflow.
28
+
- If the user asks for MCP, say this skill intentionally avoids MCP and can be extended later if needed.
29
+
30
+
## Core workflows
31
+
32
+
### Clone a Tangled repo
33
+
34
+
Use the URL shown by Tangled when possible. Common forms:
35
+
36
+
```bash
37
+
git clone https://tangled.org/OWNER/REPO
38
+
git clone git@tangled.org:OWNER/REPO
39
+
```
40
+
41
+
With the `tang` CLI, if installed:
42
+
43
+
```bash
44
+
tang repo clone OWNER/REPO
45
+
```
46
+
47
+
### Push an existing repo to Tangled
48
+
49
+
1. Confirm the user already created the Tangled repository or use a CLI to create it.
50
+
2. Add or update the remote.
51
+
3. Push branches and tags intentionally.
52
+
53
+
```bash
54
+
git remote add tangled git@tangled.org:OWNER/REPO
55
+
git push -u tangled main
56
+
git push tangled --tags
57
+
```
58
+
59
+
For a full migration:
60
+
61
+
```bash
62
+
git push -u tangled --all
63
+
git push -u tangled --tags
64
+
```
65
+
66
+
### Mirror GitHub and Tangled
67
+
68
+
For separate control, prefer separate remotes:
69
+
70
+
```bash
71
+
git remote add github git@github.com:OWNER/REPO.git
72
+
git remote add tangled git@tangled.org:OWNER/REPO
73
+
git push github main
74
+
git push tangled main
75
+
```
76
+
77
+
For one remote that pushes to both, see `references/git-ops.md`.
78
+
79
+
### Create issues and PRs
80
+
81
+
If a Tangled CLI is installed, prefer it over hand-crafting AT Protocol records:
82
+
83
+
```bash
84
+
tang issue list
85
+
tang issue create "Bug: title" --body "Details"
86
+
tang pr create --base main --head my-branch --title "Add feature" --body-file ./pr.md
87
+
```
88
+
89
+
Command names and flags differ across community CLIs. Verify with `tang --help`, `tng --help`, or `tangled --help` before executing.
90
+
91
+
## Reference files
92
+
93
+
- `references/github-mapping.md` — GitHub-to-Tangled concept and command mapping.
94
+
- `references/git-ops.md` — clone, remote setup, migration, mirroring, SSH remotes.
95
+
- `references/cli.md` — known Tangled CLI options and safe CLI selection.
96
+
- `references/issues-prs.md` — issue and pull request workflows.
97
+
- `references/knots-spindles-webhooks.md` — knots, Spindle CI/CD, webhooks.
98
+
- `references/atproto-troubleshooting.md` — DID/PDS/handle basics and common failures.
99
+
100
+
## Primary sources
101
+
102
+
Use these as the source of truth when current behavior matters:
103
+
104
+
- Tangled docs: https://docs.tangled.org/
105
+
- Quick start: https://docs.tangled.org/quick-start-guide
106
+
- Single-page docs: https://docs.tangled.org/single-page
107
+
- Webhooks: https://docs.tangled.org/webhooks
108
+
- Tangled platform: https://tangled.org/
109
+
- `tang` CLI repository: https://github.com/onevcat/tang
+88
.agents/skills/tangled/references/atproto-troubleshooting.md
+88
.agents/skills/tangled/references/atproto-troubleshooting.md
···
1
+
# AT Protocol basics and troubleshooting
2
+
3
+
Use this when Tangled identity, authentication, SSH, appview visibility, or verification is confusing.
4
+
5
+
## Concepts
6
+
7
+
- **Handle**: human-readable AT Protocol identifier, often similar to a Bluesky handle.
8
+
- **DID**: decentralized identifier, stable identity used internally by AT Protocol records.
9
+
- **PDS**: Personal Data Server that stores the user's AT Protocol data.
10
+
- **App password**: credential often used by CLIs to authenticate against a PDS. Treat as secret.
11
+
- **AppView**: tangled.org's consolidated view into repositories and collaboration records.
12
+
- **Knot**: server hosting Git repositories.
13
+
14
+
## Auth troubleshooting
15
+
16
+
Symptoms:
17
+
18
+
- CLI cannot login
19
+
- CLI says token expired
20
+
- wrong account/handle appears
21
+
- issue/PR commands fail despite Git clone working
22
+
23
+
Checks:
24
+
25
+
```bash
26
+
tang auth status
27
+
# or equivalent CLI command
28
+
29
+
tang status
30
+
```
31
+
32
+
Actions:
33
+
34
+
- Confirm handle/PDS URL.
35
+
- Refresh or re-login with the CLI.
36
+
- Use an app password, not the main account password, when the CLI expects app-password auth.
37
+
- Do not paste credentials into chat or commit them.
38
+
39
+
## SSH troubleshooting
40
+
41
+
Symptoms:
42
+
43
+
- `Permission denied (publickey)`
44
+
- clone/push fails over SSH
45
+
- HTTPS clone works but SSH does not
46
+
47
+
Checks:
48
+
49
+
```bash
50
+
git remote -v
51
+
ssh -T git@tangled.org
52
+
ssh -vT git@tangled.org
53
+
```
54
+
55
+
Actions:
56
+
57
+
- Ensure the public key is added to Tangled.
58
+
- Ensure the private key exists locally and is selected by SSH config.
59
+
- If multiple keys exist, add a host block to `~/.ssh/config`.
60
+
- After adding a key, allow for indexing/propagation delay if the CLI/docs mention it.
61
+
62
+
Example SSH config pattern:
63
+
64
+
```sshconfig
65
+
Host tangled.org
66
+
HostName tangled.org
67
+
User git
68
+
IdentityFile ~/.ssh/id_ed25519
69
+
IdentitiesOnly yes
70
+
```
71
+
72
+
## Repo visibility and empty repo issues
73
+
74
+
- A newly created empty repo may not resolve in all views until at least one commit is pushed.
75
+
- Some community CLI docs note that records created outside the web UI may lag appview ingestion. If a repo/PR exists but is not visible on tangled.org, verify with CLI/context and check current platform issue status.
76
+
77
+
## Commit verification
78
+
79
+
If commits are not marked verified:
80
+
81
+
- Check whether Tangled supports the signature type being used.
82
+
- Confirm the signing key is associated with the correct identity/account.
83
+
- Verify local Git signing configuration.
84
+
- Refer to the official Tangled troubleshooting docs for current behavior.
85
+
86
+
## General rule
87
+
88
+
When Tangled behavior differs from GitHub, do not force a GitHub mental model. Identify whether the issue is in Git transport, AT Protocol auth/records, appview indexing, or knot hosting.
+75
.agents/skills/tangled/references/cli.md
+75
.agents/skills/tangled/references/cli.md
···
1
+
# Tangled CLI reference
2
+
3
+
Tangled has multiple community CLIs. Do not assume one is installed or canonical. Verify before using.
4
+
5
+
## Detect available CLIs
6
+
7
+
```bash
8
+
command -v tang || true
9
+
command -v tng || true
10
+
command -v tangled || true
11
+
```
12
+
13
+
Then inspect help:
14
+
15
+
```bash
16
+
tang --help
17
+
# or
18
+
tng --help
19
+
# or
20
+
tangled --help
21
+
```
22
+
23
+
## Known CLIs
24
+
25
+
### `tang` by onevcat
26
+
27
+
Source: https://github.com/onevcat/tang
28
+
29
+
Designed for day-to-day Tangled repository work:
30
+
31
+
- `auth`: login, logout, token refresh, token inspection, auth status
32
+
- `status`: combined auth, repo, and service status
33
+
- `config`: knot, AppView, Constellation, preferred git remote, clone protocol
34
+
- `ssh-key`: list/add/delete Tangled SSH public keys
35
+
- `repo`: view/list/create/clone repositories
36
+
- `issue`: list/create/view/edit/comment/close/reopen issues
37
+
- `pr`: list/create/view/diff/comment/checkout/close/reopen/merge pull requests
38
+
- `browse`: open Tangled pages from current repo context
39
+
- `completion`: shell completions
40
+
41
+
Examples:
42
+
43
+
```bash
44
+
tang auth status
45
+
tang status
46
+
tang config get clone.protocol
47
+
tang config set clone.protocol ssh
48
+
49
+
tang ssh-key list
50
+
tang repo clone OWNER/REPO
51
+
tang repo create my-project --knot KNOT_HOST
52
+
53
+
tang issue list
54
+
tang issue create "Bug: title" --body "Details"
55
+
56
+
git push origin my-branch
57
+
tang pr create --base main --head my-branch --title "Add feature" --body-file ./pr.md
58
+
```
59
+
60
+
Caveats from the README:
61
+
62
+
- `repo create` may require a create-capable knot; pass `--knot` when the default route is insufficient.
63
+
- SSH clone may depend on Tangled's SSH key authorization index; after adding a key, retry after key list/index refresh.
64
+
- PR merge uses Tangled's merge endpoint and may not support GitHub-style squash/rebase strategies.
65
+
66
+
### `tng` and other CLIs
67
+
68
+
Other community CLIs exist and may expose similar functions: auth, repo, issue, PR, SSH key, context/config. Their flags and output formats can differ. Use help output as the immediate source of truth.
69
+
70
+
## CLI selection policy
71
+
72
+
- If `tang` is installed, prefer it because it has broad documented coverage.
73
+
- If another CLI is already installed in the user's environment, do not replace it without asking.
74
+
- If no CLI is installed and the task can be done with Git, use Git.
75
+
- If no CLI is installed and the task requires issues/PRs/repo creation, ask whether to install a CLI or use the Tangled web UI.
+90
.agents/skills/tangled/references/git-ops.md
+90
.agents/skills/tangled/references/git-ops.md
···
1
+
# Tangled Git operations
2
+
3
+
Use standard Git for clone, fetch, pull, push, remote migration, and mirroring.
4
+
5
+
## Inspect current repo
6
+
7
+
```bash
8
+
git status
9
+
git remote -v
10
+
git branch --show-current
11
+
```
12
+
13
+
## Common remote URL forms
14
+
15
+
Use the exact URL shown by Tangled when possible. Common examples:
16
+
17
+
```bash
18
+
https://tangled.org/OWNER/REPO
19
+
git@tangled.org:OWNER/REPO
20
+
git@tangled.org:user.tngl.sh/my-project
21
+
```
22
+
23
+
Older docs/examples may show `user.tngl.sh/my-project`; current repos may also use handle or DID forms. Verify from Tangled UI or CLI before writing remotes.
24
+
25
+
## Add Tangled as a separate remote
26
+
27
+
This is safest when the user wants explicit control.
28
+
29
+
```bash
30
+
git remote add tangled git@tangled.org:OWNER/REPO
31
+
git push -u tangled main
32
+
git push tangled --tags
33
+
```
34
+
35
+
## Change origin to Tangled
36
+
37
+
Use only when the user wants Tangled as the primary remote.
38
+
39
+
```bash
40
+
git remote set-url origin git@tangled.org:OWNER/REPO
41
+
git push -u origin --all
42
+
git push -u origin --tags
43
+
```
44
+
45
+
## Mirror while keeping GitHub as primary
46
+
47
+
### Separate remotes
48
+
49
+
```bash
50
+
git remote add github git@github.com:OWNER/REPO.git
51
+
git remote add tangled git@tangled.org:OWNER/REPO
52
+
53
+
git push github main
54
+
git push tangled main
55
+
```
56
+
57
+
### One remote with multiple push URLs
58
+
59
+
Use when the user wants `git push origin main` to push to both GitHub and Tangled.
60
+
61
+
```bash
62
+
# Keep fetch URL as the primary remote, then reset push URLs explicitly.
63
+
git remote set-url origin git@github.com:OWNER/REPO.git
64
+
65
+
git remote set-url --add --push origin git@github.com:OWNER/REPO.git
66
+
git remote set-url --add --push origin git@tangled.org:OWNER/REPO
67
+
68
+
git remote -v
69
+
git push origin main
70
+
```
71
+
72
+
After adding multiple push URLs, `git remote -v` should show one fetch URL and multiple push URLs.
73
+
74
+
## Full migration
75
+
76
+
```bash
77
+
git push -u tangled --all
78
+
git push -u tangled --tags
79
+
```
80
+
81
+
State clearly: this transfers Git refs and history, not GitHub issues, PRs, discussions, releases, or project metadata unless another tool handles them.
82
+
83
+
## SSH checks
84
+
85
+
```bash
86
+
ssh -T git@tangled.org
87
+
ssh -vT git@tangled.org
88
+
```
89
+
90
+
If SSH fails, check that the public key is uploaded to Tangled, the correct key is selected in `~/.ssh/config`, and the repo URL matches the target owner/repo.
+25
.agents/skills/tangled/references/github-mapping.md
+25
.agents/skills/tangled/references/github-mapping.md
···
1
+
# GitHub to Tangled mapping
2
+
3
+
Use this when translating familiar GitHub workflows into Tangled workflows.
4
+
5
+
| GitHub concept | Tangled equivalent / note |
6
+
|---|---|
7
+
| `github.com` | `tangled.org` appview plus distributed knots |
8
+
| GitHub user/org | AT Protocol handle/DID; repositories are associated with ATProto identity records and hosted on knots |
9
+
| GitHub repository hosting | Tangled knot hosting Git data |
10
+
| GitHub web UI | Tangled appview at `tangled.org` |
11
+
| `gh repo clone` | `git clone ...` or `tang repo clone OWNER/REPO` if CLI installed |
12
+
| `gh repo create` | Tangled web UI or `tang repo create`/`tng repo create` if CLI installed and a create-capable knot is available |
13
+
| GitHub Issues | Tangled issue records; use Tangled web UI or CLI |
14
+
| GitHub Pull Requests | Tangled PR records and patches; use Tangled web UI or CLI |
15
+
| GitHub Actions | Spindles workflows under `.tangled/workflows/` |
16
+
| GitHub webhooks | Tangled webhooks; currently push events are documented |
17
+
| GitHub SSH keys | Tangled SSH public keys, often managed through web UI or `tang ssh-key` |
18
+
19
+
## Important differences
20
+
21
+
- Tangled is decentralized. A repo may be visible through the appview but hosted by a knot.
22
+
- Identity is AT Protocol based: handles, DIDs, and PDS matter for auth and record ownership.
23
+
- Basic migration from GitHub/GitLab is Git history only: change/add remotes and push branches/tags. Issues/PRs are not migrated by plain Git.
24
+
- PR merge strategies may be narrower than GitHub. The `tang` README notes no GitHub-style squash/rebase strategies for its current merge endpoint.
25
+
- Community CLIs may lag platform behavior. Verify with current docs and CLI help.
+72
.agents/skills/tangled/references/issues-prs.md
+72
.agents/skills/tangled/references/issues-prs.md
···
1
+
# Tangled issues and pull requests
2
+
3
+
Use this when the user asks to create, view, comment on, close, reopen, review, checkout, or merge Tangled issues/PRs.
4
+
5
+
## Before acting
6
+
7
+
1. Confirm the current repository context.
8
+
2. Check whether a Tangled CLI is installed.
9
+
3. Inspect command help because CLI flags differ.
10
+
4. For write operations, summarize what will be created/changed before running commands when the action is not obviously requested.
11
+
12
+
```bash
13
+
git remote -v
14
+
command -v tang || command -v tng || command -v tangled || true
15
+
```
16
+
17
+
With `tang`:
18
+
19
+
```bash
20
+
tang status
21
+
tang issue list
22
+
tang pr list
23
+
```
24
+
25
+
## Issues with `tang`
26
+
27
+
```bash
28
+
tang issue list
29
+
tang issue view 5
30
+
tang issue create "Bug: title" --body "Detailed description"
31
+
tang issue comment 5 --body "Comment text"
32
+
tang issue close 5
33
+
tang issue reopen 5
34
+
```
35
+
36
+
If body content is long, prefer file/stdin patterns if supported:
37
+
38
+
```bash
39
+
tang issue create "Bug: title" --body-file ./issue.md
40
+
```
41
+
42
+
## Pull requests with `tang`
43
+
44
+
Typical flow:
45
+
46
+
```bash
47
+
git checkout -b my-branch
48
+
# edit files
49
+
git push -u origin my-branch
50
+
51
+
tang pr create --base main --head my-branch --title "Add feature" --body-file ./pr.md
52
+
```
53
+
54
+
Common operations:
55
+
56
+
```bash
57
+
tang pr list
58
+
tang pr view 3
59
+
tang pr diff 3
60
+
tang pr comment 3 --body "Looks good."
61
+
tang pr checkout 3
62
+
tang pr close 3
63
+
tang pr reopen 3
64
+
tang pr merge 3
65
+
```
66
+
67
+
## Caveats
68
+
69
+
- Tangled PR identifiers may be numeric in appview contexts or ATProto rkeys in some CLIs. Use the CLI's list/view output to choose the correct identifier.
70
+
- PR patches and comments may be stored as ATProto records/blobs depending on CLI implementation.
71
+
- Do not assume GitHub semantics like squash merge, rebase merge, required reviews, or branch protection unless the current Tangled docs/CLI confirm them.
72
+
- If the user asks to migrate GitHub issues/PRs, do not promise built-in migration. Treat it as a separate import/export project.
+71
.agents/skills/tangled/references/knots-spindles-webhooks.md
+71
.agents/skills/tangled/references/knots-spindles-webhooks.md
···
1
+
# Knots, Spindles, and webhooks
2
+
3
+
Use this for Tangled hosting architecture, CI/CD, and automation.
4
+
5
+
## Knots
6
+
7
+
A knot is a lightweight headless server that hosts Git repositories. Tangled provides managed knots, and users can self-host knots for single-user, home-lab, or community setups.
8
+
9
+
Operational implications:
10
+
11
+
- Repo creation may require choosing a create-capable knot.
12
+
- A repo can be accessible through the tangled.org appview while its Git data lives on a knot.
13
+
- When a CLI asks for `--knot`, use the knot host intended to host the repository.
14
+
- Self-hosted knot troubleshooting should rely on official docs and service logs.
15
+
16
+
## Spindles CI/CD
17
+
18
+
Spindles are Tangled's CI/CD workflows. Workflow files live under:
19
+
20
+
```text
21
+
.tangled/workflows/
22
+
```
23
+
24
+
They are YAML files. Official docs describe triggers such as:
25
+
26
+
- `push` — run when a commit is pushed
27
+
- `pull_request` — run when a pull request is made or updated
28
+
- manual trigger support may exist depending on current docs
29
+
30
+
Workflow clone behavior can be customized with a `clone` field. Documented clone options include:
31
+
32
+
- `skip`: skip cloning when the workflow does not need repo contents
33
+
- `depth`: fetch limited commit history; default examples mention shallow clone behavior
34
+
- `submodules`: fetch Git submodules recursively when needed
35
+
36
+
When creating or editing workflows:
37
+
38
+
1. Check existing `.tangled/workflows/` files first.
39
+
2. Keep YAML minimal and explicit.
40
+
3. Match trigger names and fields to the current official docs.
41
+
4. Do not invent GitHub Actions syntax unless Tangled docs state compatibility.
42
+
43
+
## Webhooks
44
+
45
+
Official docs: https://docs.tangled.org/webhooks
46
+
47
+
Tangled webhooks send HTTP POST notifications to configured URLs. The documented event type is currently `push`.
48
+
49
+
Setup fields:
50
+
51
+
- Payload URL
52
+
- Optional secret for signature verification
53
+
- Events, currently push
54
+
- Active enabled/disabled state
55
+
56
+
Typical headers:
57
+
58
+
- `Content-Type: application/json`
59
+
- `User-Agent: Tangled-Hook/...`
60
+
- `X-Tangled-Event: push`
61
+
- `X-Tangled-Hook-ID`
62
+
- `X-Tangled-Delivery`
63
+
- `X-Tangled-Signature-256: sha256=...` when a secret is configured
64
+
65
+
Webhook payload includes before/after SHAs, ref, pusher DID, and repository metadata such as clone URL, HTML URL, SSH URL, name, full name, owner DID, counts, and timestamps.
66
+
67
+
When implementing a receiver:
68
+
69
+
- Verify HMAC-SHA256 if a secret is configured.
70
+
- Respond quickly with 2xx; do longer work asynchronously to avoid retries/timeouts.
71
+
- Avoid logging secrets or full payloads if they contain sensitive metadata.
+6
skills-lock.json
+6
skills-lock.json
···
250
250
"skillPath": "skills/writing-plans/SKILL.md",
251
251
"computedHash": "8990dd5cab321e8128c76684c490eb150f4f5d4b1df14e8f6ee0177b0b92937a"
252
252
},
253
+
"tangled": {
254
+
"source": "git@tangled.org:homebodify.tngl.sh/tangled-skill",
255
+
"sourceType": "git",
256
+
"skillPath": "SKILL.md",
257
+
"computedHash": "9b4c75735748bfd66fd4c05765f02e1d46ccf13a35508f8c44c83a2cafa3d79d"
258
+
},
253
259
"telemetry-capture": {
254
260
"source": "dagger/dagger",
255
261
"ref": "main",