Skip to content
Back to skills

Add Team Source

ASecurity

Register a git URL as a team-profile source so nyann can periodically sync and expose its profiles under a namespace. TRIGGER when the user says "add a team profile source", "register a team profile source", "set up team profiles from <url>", "wire up our team's shared profiles at <repo>", "add profile source named X at <url>", "install team profiles from <git repo>", "/nyann:add-team-source". Do NOT trigger on "sync team profiles now" (that's `sync-team-profiles` — the pull operation). Do NO...

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
developmenttestinggitbackend

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add thettwe/nyann --skill add-team-source --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Add Team Source?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Add Team Source
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thettwe-add-team-source/badge)](https://www.skillsdirectory.com/skills/thettwe-add-team-source)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: add-team-source
description: >
  Register a git URL as a team-profile source so nyann can periodically
  sync and expose its profiles under a namespace.
  TRIGGER when the user says "add a team profile source", "register a
  team profile source", "set up team profiles from <url>", "wire up
  our team's shared profiles at <repo>", "add profile source named
  X at <url>", "install team profiles from <git repo>",
  "/nyann:add-team-source".
  Do NOT trigger on "sync team profiles now" (that's
  `sync-team-profiles` — the pull operation). Do NOT trigger on
  "save my setup as a profile" (that's `learn-profile` — writes to
  user root, not a team source). Do NOT trigger on generic "add a
  repo" or "add a remote" — those are git operations unrelated to
  profile distribution.
---

# add-team-source

Wraps `bin/add-team-source.sh`. Updates
`~/.claude/nyann/config.json` to declare a new team-profile source.
Idempotent — passing the same `--name` updates the entry in place.

## 1. Collect inputs

- **`--name <id>`** — required. Short slug, `^[a-z0-9][a-z0-9-]*$`.
  Will also become the namespace prefix for team profiles (e.g.
  `platform-team/base` when name is `platform-team`). When the user
  gives a name with spaces or caps, propose a slug and confirm.
- **`--url <git-url>`** — required. Any URL git can clone
  (https://, git@, file:// for testing).
- **`--ref <branch-or-tag>`** — default `main`. Override when the
  team pins a specific branch or tag.
- **`--interval <hours>`** — default `24`. How often
  `sync-team-profiles` will re-pull from this source without
  `--force`. Decrease only when the user says "we update these
  often" or similar.

## 2. Pre-flight

- Config path defaults to `~/.claude/nyann/config.json`. Override
  only when the user explicitly names a different user root.
- The backend upserts on `--name` collision. Warn the user if
  they're replacing an existing source with a different URL —
  that's usually unintentional. Read current config first if unsure.

## 3. Invoke

```
bin/add-team-source.sh \
  --name <id> \
  --url <git-url> \
  [--ref <branch>] \
  [--interval <hours>] \
  [--user-root <dir>]
```

Exit 0 on success; config path is logged to stderr.

## 4. Report back

- Name, URL, ref, interval.
- Tell the user "Run `/nyann:sync-team-profiles` (or ask 'sync my
  team profiles') to actually pull them". `add-team-source` only
  registers — the pull is a separate operation on purpose (no
  surprise network calls here).

## When to hand off

- "Now pull them" → `sync-team-profiles` skill.
- "Apply a team profile to this repo" → `bootstrap-project` with
  the namespaced profile name (e.g. `platform-team/base`).
- "Show what the team profile does" → `inspect-profile` with the
  namespaced name.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.