Automated summary
This skill provides a map of the TTA.dev CLI subsystem (the cmd_status command and related code), listing key files, symbols and entry points to make navigating the codebase easier.
Strengths
- Points straight at entry points such as cmd_status in ttadev/cli/status.py, skipping lengthy exploration
- Lists key files with their symbols and associated tests, giving a quick sense of where behavior and coverage live
- Pairs source modules with their test files (test_status.py, test_setup.py), which helps change behavior and assertions together
- States clearly when to use it, including work on cmd_status and the key-validation logic
Limitations
- It is a generated static index (110 symbols, 27 files, 70% cohesion), so line numbers and counts can go stale
- Scope is one repository's cli subsystem only, with no architectural rationale or coding conventions
- The execution-flows table is truncated in the provided document, so it offers little usable detail
Use it when you need to locate or modify CLI-related code in TTA.dev, especially cmd_status, provider key validation, or their tests.
Avoid it when designing a CLI unrelated to TTA.dev or when you need architectural explanation that this plain index does not provide.
Security analysis
SafeThe skill is a purely descriptive index of an existing CLI subsystem: file paths, symbol names, test names, and navigation hints. It declares no allowed tools, contains no shell commands, no network calls, no credential handling, and no obfuscated payloads. The only actionable references are to gitnexus_context/gitnexus_query use, which are benign lookup helpers. Listing it introduces no execution risk.
No concerns found
How this analysis is madeExamples
In TTA.dev, add a --verbose flag to cmd_status that prints per-provider latency, and update the related tests in tests/cli/test_status.py.Where is the exit code of the `ttadev setup` command decided when no provider is connected? Show me the relevant functions in ttadev/cli/setup.py and the tests that cover them.Give me the entry points and key symbols of the TTA.dev CLI subsystem so I can start working on the status and models commands.name: cli description: "Cli subsystem in TTA.dev: cmd_status and related code. 110 symbols | 27 files | Cohesion: 70%"
Cli
110 symbols | 27 files | Cohesion: 70%
When to Use
- Working on
cli-related functionality in TTA.dev - Modifying
cmd_status - Navigating
ttadev/cli/run.py,ttadev/cli/models.py
Key Files
| File | Symbols |
|------|---------|
| tests/cli/test_status.py | _args, _make_validation_result, _make_ok_result, test_exit_code_zero_when_providers_healthy, test_output_contains_checkmark_for_healthy_provider (+14) |
| tests/cli/test_setup.py | _make_args, test_exit_0_when_at_least_one_connected, test_exit_1_when_none_connected, test_json_output_parses, test_json_output_no_key_values (+8) |
| ttadev/cli/run.py | execute, _path, get, set, run_cache (+5) |
| ttadev/cli/models.py | handle_model_command, _cmd_suggest_qwen, _cmd_ollama, _cmd_ollama_recommend, _cmd_info (+5) |
| ttadev/cli/control.py | _step_duration, _handle_task_create, _handle_task_list, _handle_task_show, _handle_task_claim (+4) |
| ttadev/cli/setup.py | _get_key, cmd_validate_keys, validate_provider, _read_env, _write_env (+4) |
| ttadev/cli/benchmark.py | _validate_response, _benchmark_model, run_benchmark, cmd_benchmark, _run (+2) |
| ttadev/cli/status.py | _provider_slug, _check_port, cmd_status, _count_control_plane |
| ttadev/cli/hw_detect.py | detect_gpu_vram_gb, detect_system_ram_gb, recommend_ollama_model, hardware_summary |
| tests/unit/test_hw_detect.py | _with_gpu, _no_gpu, test_recommended_model_matches_standalone_recommend |
Entry Points
Start here when exploring this area:
cmd_status(Function) —ttadev/cli/status.py:122test_exit_code_zero_when_providers_healthy(Function) —tests/cli/test_status.py:200test_output_contains_checkmark_for_healthy_provider(Function) —tests/cli/test_status.py:216test_output_shows_latency_for_healthy_providers(Function) —tests/cli/test_status.py:240test_exit_code_one_when_all_missing(Function) —tests/cli/test_status.py:266
Key Symbols
| Symbol | Type | File | Line |
|--------|------|------|------|
| cmd_status | Function | ttadev/cli/status.py | 122 |
| test_exit_code_zero_when_providers_healthy | Function | tests/cli/test_status.py | 200 |
| test_output_contains_checkmark_for_healthy_provider | Function | tests/cli/test_status.py | 216 |
| test_output_shows_latency_for_healthy_providers | Function | tests/cli/test_status.py | 240 |
| test_exit_code_one_when_all_missing | Function | tests/cli/test_status.py | 266 |
| test_output_shows_missing_key_message | Function | tests/cli/test_status.py | 282 |
| test_json_output_is_valid_json | Function | tests/cli/test_status.py | 304 |
| test_json_output_has_required_keys | Function | tests/cli/test_status.py | 324 |
| test_json_output_contains_no_key_values | Function | tests/cli/test_status.py | 342 |
| test_json_healthy_true_when_provider_connected | Function | tests/cli/test_status.py | 361 |
| test_json_healthy_false_when_all_fail | Function | tests/cli/test_status.py | 378 |
| test_dashboard_running_shown_in_output | Function | tests/cli/test_status.py | 399 |
| test_mcp_running_shown_in_output | Function | tests/cli/test_status.py | 417 |
| test_json_services_reflect_port_state | Function | tests/cli/test_status.py | 434 |
| test_control_plane_counts_in_human_output | Function | tests/cli/test_status.py | 455 |
| test_control_plane_counts_in_json_output | Function | tests/cli/test_status.py | 471 |
| cmd_validate_keys | Function | ttadev/cli/setup.py | 314 |
| test_exit_0_when_at_least_one_connected | Function | tests/cli/test_setup.py | 281 |
| test_exit_1_when_none_connected | Function | tests/cli/test_setup.py | 296 |
| test_json_output_parses | Function | tests/cli/test_setup.py | 309 |
Execution Flows
| Flow | Type | Steps |
|------|------|-------|
| Handle_model_command → Rank_models_for_task | cross_community | 6 |
| Handle_model_command → _classify_entry | cross_community | 6 |
| Handle_model_command → Estimate_finetune_cost | cross_community | 5 |
| Handle_model_command → Estimate_quality_improvement | cross_community | 5 |
| Handle_model_command → Calculate_roi_breakeven | cross_community | 5 |
| Main → _path | cross_community | 4 |
| Handle_model_command → _build_rationale | intra_community | 4 |
| Main → Register_agent_subcommands | cross_community | 3 |
| Main → Register_agents_subcommands | cross_community | 3 |
| Main → Register_workflow_subcommands | cross_community | 3 |
Connected Areas
| Area | Connections | |------|-------------| | Unit | 36 calls | | Control_plane | 4 calls | | Observability | 3 calls | | Model_advisor | 2 calls | | Agents | 1 calls |
How to Explore
gitnexus_context({name: "cmd_status"})— see callers and calleesgitnexus_query({query: "cli"})— find related execution flows- Read key files listed above for implementation details
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/cli-subsystem-mrwak9rk/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/cli-subsystem-mrwak9rk' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/cli-subsystem-mrwak9rk/download' --output '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md.part' && mv '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md.part' '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && test -s '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/cli' && cp -R '.skill-downloads/cli-subsystem-mrwak9rk' '.claude/skills/cli'Cursor
test -f '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && test -s '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/cli' && cp -R '.skill-downloads/cli-subsystem-mrwak9rk' '.cursor/skills/cli'Codex
test -f '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && test -s '.skill-downloads/cli-subsystem-mrwak9rk/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/cli' && cp -R '.skill-downloads/cli-subsystem-mrwak9rk' '.agents/skills/cli'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/cli-subsystem-mrwak9rk'openskills read 'cli-subsystem-mrwak9rk'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/cli-subsystem-mrwak9rk/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.