ZacharyZhang-NY
d6c20fc13f
Hard fork of xai-org/grok-build (Apache-2.0) re-targeted as Kigi, an
unofficial Kimi Code CLI community build.
Rename & identity
- 72 xai-*/xai-grok-* crates -> kigi-* (explicit: xai-grok-pager-bin ->
kigi-bin [binary `kigi`], xai-grok-pager -> kigi-tui; rest mechanical);
ptyctl, ptyctl-cli, third_party/ unchanged; proto package
xai.grok.tools.v1 -> kigi.tools.v1
- Config home ~/.kigi (KIGI_SHARE_DIR override), env prefix GROK_* ->
KIGI_*, `kigi --version` carries the unofficial-community-build notice
- clap identity, help text, startup banner, prompt templates rebranded
(templates re-encrypted)
Deletions (PRD removal list #5/#6/#7/#9/#10)
- voice input (xai-grok-voice) and all TUI wiring
- telemetry: Mixpanel client, external OTel stream, Sentry, OTLP layers,
trace/GCS/S3 upload queues (kigi-file-utils halved), workspace upload
module & dc_log, heap-profile uploader, auth-diagnostics uploader,
session-analytics halves of feedback; local zero-egress observability
preserved in new kigi-log crate (unified log, --debug firehose,
subsystem file logs, opt-in instrumentation)
- announcements (crate, remote-settings fields, TUI surfaces)
- plugin marketplace (crate, sources/browse/CTA/extensions-modal tab);
direct plugin install/uninstall/update via kigi-agent git_install kept
- relay/gateway/assets endpoints and features (agent relay, headless
relay transport, gateway bridge, LeaderEnvUrls); leader IPC socket now
~/.kigi/leader.sock + KIGI_LEADER_SOCKET, no ws-url derivation
- functional types rehomed instead of deleted: PermissionMode ->
kigi-config-types, McpInitStrategy -> kigi-mcp, PrCreationSource ->
session signals, TerminalDiagnostics -> kigi-pager-render, agent_id ->
shell util
Endpoints
- kigi-env rewritten: single production KigiEndpoints {coding_api_base_url
https://api.kimi.com/coding/v1 (KIGI_CODE_BASE_URL), oauth_host
https://auth.kimi.com (KIGI_OAUTH_HOST), update_base_url (GitHub
Releases API), upgrade_page_url}; GrokBuildEnvironment enum deleted
Toolchain & workspace hygiene
- Rust 1.97.0 pinned; edition 2024; full cargo update; git2 hoisted to
workspace at 0.21 (Option->Result API migration), quick-xml 0.41
- Root Cargo.toml hand-maintained (PRD §8.1): version 0.1.0 inherited by
all members, members sorted, unused deps pruned
- cargo-deny advisories gate (deny.toml with documented transitive
exceptions); CI workflow (check/clippy/fmt/deny/test, macOS+Linux)
- cross-crate test seams re-gated behind `test-support` cargo feature;
insta snapshot baselines renamed to the kigi_tui prefix
- clippy --workspace --all-targets: zero warnings; fmt clean
Fixes surfaced by the port
- updater probe/installer divergence (bin/kigi vs bin/grok symlink set)
- idle model-metadata refresh dead under KIGI_CODE_BASE_URL override
(new is_effective_coding_endpoint_url, loopback+override aware)
- macOS symlinked-TMPDIR fixture canonicalization (foreign_sessions,
fast-worktree); RSS measurement tests serialized via serial_test
Docs & legal (Apache §4)
- NOTICE added (upstream attribution + change statement); THIRD-PARTY
notices sustained; kigi-tools ported-code notices extended; README,
CONTRIBUTING, SECURITY, AGENTS.md rewritten
Out of scope for M0 (tracked): Kimi auth/inference (M1), search/fetch,
command parity, config import (M2), Computer Hub excision & final
brand-token sweep (M2), distribution & self-update rewrite (M3).
81 lines
3.2 KiB
Markdown
81 lines
3.2 KiB
Markdown
---
|
|
name: create-skill
|
|
description: >
|
|
Interactively create a new Grok skill (SKILL.md + optional scripts/references).
|
|
Use when the user wants to create a skill, scaffold a skill, or runs /create-skill.
|
|
metadata:
|
|
short-description: "Create a new Grok skill"
|
|
---
|
|
|
|
# Create Skill
|
|
|
|
Interactively gather requirements from the user and create a fully working Grok skill on disk.
|
|
|
|
## Step 1: Gather information
|
|
|
|
Ask the user the following questions **one at a time as regular conversation questions** (do NOT use structured option prompts for free-text inputs):
|
|
|
|
1. **Skill name** - ask the user to type a name. Lowercase letters (a-z), digits (0-9), and hyphens (-) only. Must start and end with a letter or digit. Must be 2-64 characters long (e.g. `deploy-k8s`). Validate the name before proceeding.
|
|
2. **Scope** - present the user with two options:
|
|
- **Project** (Recommended): `<repo-root>/.kigi/skills/<name>/SKILL.md` - available only in this repo, shareable with teammates
|
|
- **User**: `~/.kigi/skills/<name>/SKILL.md` - available in all projects
|
|
- Default to **Project** if inside a git repo, otherwise **User**.
|
|
3. **What it should do** - ask the user to describe the workflow, paste an example prompt they keep repeating, or explain the task the skill should automate.
|
|
|
|
## Step 2: Draft the description
|
|
|
|
Write a `description` frontmatter value that includes:
|
|
- What the skill does (1-2 sentences)
|
|
- Trigger phrases and keywords so Grok knows when to auto-invoke it
|
|
- The slash command name (e.g. "Use when the user runs /deploy-k8s")
|
|
|
|
Show the drafted description to the user and let them approve or edit it.
|
|
|
|
## Step 3: Create the directory
|
|
|
|
Run this bash command to create the skill directory:
|
|
|
|
```bash
|
|
mkdir -p <SKILL_DIR>
|
|
```
|
|
|
|
Where `<SKILL_DIR>` is:
|
|
- User scope: `~/.kigi/skills/<name>`
|
|
- Project scope: `<repo-root>/.kigi/skills/<name>`
|
|
|
|
If the skill needs helper scripts, also create `<SKILL_DIR>/scripts/`.
|
|
If the skill needs reference docs, also create `<SKILL_DIR>/references/`.
|
|
|
|
## Step 4: Write SKILL.md
|
|
|
|
Use `search_replace` with an empty `old_string` to create the file at `<SKILL_DIR>/SKILL.md`.
|
|
|
|
The file MUST follow this exact format:
|
|
|
|
```
|
|
---
|
|
name: <skill-name>
|
|
description: <the description from Step 2>
|
|
---
|
|
|
|
<markdown body with instructions, steps, code blocks>
|
|
```
|
|
|
|
Also write any supporting files (scripts, references) using the same create method.
|
|
|
|
## Step 5: Verify and confirm
|
|
|
|
1. Run `cat <SKILL_DIR>/SKILL.md` to verify the file was written correctly.
|
|
2. Tell the user the skill is ready and how to use it:
|
|
- Slash command: `/<skill-name>`
|
|
- TUI menu: `/skills <skill-name>`
|
|
- Automatic: Grok will invoke it when the description matches user intent
|
|
3. Tell the user the skill should appear in the slash menu within a few seconds (skills auto-reload when files change on disk).
|
|
|
|
## Guidelines
|
|
|
|
- Keep the SKILL.md body focused and actionable. It is a prompt for the agent, not documentation.
|
|
- The `description` field is critical. It controls auto-invocation. Be specific with trigger words.
|
|
- Prefer referencing existing CLI tools over writing custom scripts.
|
|
- Do NOT skip creating the directory. The file will fail to save without it.
|
|
- Always use absolute paths when creating files to avoid writing to the wrong location. |