jetson-ai-lab-cli

Discord-facing knowledge fetch & index agent for the Jetson AI Lab community — fetches and indexes Jetson AI Lab docs/sources and answers members' questions on Discord.

Status: the read side is real, the rest is still scaffold. The agent can scan the Jetson AI Lab Discord read-only today (see below); indexing what it reads and answering members' questions are not built yet.

What you get

• A read-only Jetson AI Lab Discord scanner — the jetson-discord-scan skill, the first slice of the agent's actual job. See Jetson AI Lab Discord.
• An agent-first CLI cited from teken (afi-cli) — the runtime package has no third-party dependencies.
• A mesh identity — culture.yaml (suffix + backend) and the matching prompt file (CLAUDE.md for backend: claude).
• The canonical guildmaster skill kit (11 skills) under .claude/skills/, vendored cite-don't-import. See docs/skill-sources.md.
• A build + deploy baseline — pytest, lint, the agent-first rubric gate, and PyPI Trusted Publishing wired into GitHub Actions.

Quickstart

uv sync
uv run pytest -n auto                 # run the test suite
uv run jetson-ai-lab-cli whoami  # identity from culture.yaml
uv run jetson-ai-lab-cli learn   # self-teaching prompt (add --json)
uv run teken cli doctor . --strict    # the agent-first rubric gate CI runs

CLI

Every command supports --json. Results go to stdout, errors/diagnostics to stderr (never mixed). Exit codes: 0 success, 1 user error, 2 environment error, 3+ reserved.

Jetson AI Lab Discord (read-only)

The agent's intended job starts at the Jetson AI Lab Research Group Discord — a hands-on community running modern AI on NVIDIA edge hardware. At a glance:

The jetson-discord-scan skill gives it a read-only window into that server. It wraps the read verbs of the sibling discord-bot-cli — it never posts, reacts, or creates threads — and it scans public channels only (private / role-gated channels are always excluded).

S=.claude/skills/jetson-discord-scan/scripts/scan.sh

bash $S doctor                              # token present + guild readable?
bash $S active --since 30 --top 15          # public channels active in the last month, by traffic
bash $S channels                            # public channel map (each tagged "public": true)
bash $S read <channel_id> --limit 50        # recent messages of one channel

Needs a read-scoped bot token in DISCORD_BOT_TOKEN and discord-bot-cli with its [discord] extra. Results are JSON on stdout; errors/diagnostics on stderr.

Member participation statistics (jlab discord members)

jlab discord members                  # last 90 days, public text channels
jlab discord members --since 30       # narrower window
jlab discord members --json           # same statistics, id-only, on stdout

This scans the same public text channels and writes an HTML report — message counts, breadth across channels, thread/question starts, and length-based substance signals per participant — to a fixed path inside this repo, printing that path when it's done.

Expect it to take about five minutes. Measured against the Jetson AI Lab guild (100 public text channels, 90-day window): ~15s to scan and page the channels, then ~4m45s to resolve author ids to names — one fetch_member call per distinct author, 869 of them, at ~330ms each. Name resolution is ~95% of the runtime; a batch resolution verb is filed upstream as agentculture/discord-bot-cli#14 and would cut the run to well under a minute. --since 30 is proportionally faster because it finds fewer distinct authors. It issues no verdict: the CLI does not rank, score, or label anyone "most active," and it produces no presenter shortlist — it organizes statistics so a Channel Maintainer (or an agent) can read the report and make that judgment themselves.

The pipeline is anonymous end to end until the very last step: messages are aggregated by author.id only, message content never survives past the aggregation stage (only lengths and counts do), and display names are resolved from ids in one batch, solely to render the report — --json output stays id-only. Bots and webhooks are excluded; members who have left the guild are excluded by default (a flag can include everyone). Voice channels are deliberately out of scope — a member who only attends voice sessions won't show up in this report — and forum channels/threads are a possible follow-up, not covered yet. The generated report is gitignored and never committed; it's a local artifact you hand to a maintainer, not a checked-in file.

Make it your own

1. Rename the package jlab/ and the jetson-ai-lab-cli CLI/dist name throughout pyproject.toml, the package, tests/, and sonar-project.properties.
2. Edit culture.yaml with your suffix and backend.
3. Rewrite CLAUDE.md for your agent and run /init.
4. Re-vendor only the skills you need from guildmaster (see docs/skill-sources.md).

See CLAUDE.md for the full conventions (version-bump-every-PR, the cicd PR lane, deploy setup).

License

MIT — see LICENSE.