dbtinoy-dbtinoy-/lexigram-framework-skills/cli-config-and-inspect/SKILL.md

cli-config-and-inspect

Skill1 starsChanged 3 months agoMITView on GitHub

Use when viewing or validating configuration, inspecting runtime state, diagnosing system issues, or managing CLI contributors in Lexigram

Reads credentials

In this repository17 other files it gives its agents.
- ai-subsystem-quickstartSkill
- auth-and-securitySkill
- caching-patternsSkill
- cli-code-generationSkill
- cli-database-operationsSkill
- cli-project-scaffoldingSkill
- configuration-managementSkill
- creating-providers-and-modulesSkill
- database-repository-patternSkill
- events-and-messagingSkill
- lexigram-uiSkill
- multimedia-generationSkill
- real-time-webSkill
- resilience-patternsSkill
- testing-with-lexigramSkill
- using-result-and-error-codesSkill
- web-controllers-and-routingSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Not using --json for programmatic consumption — human-friendly output is fragile to parse
line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

CLI Config and Inspect

Overview

lexigram config manages application configuration. lexigram inspect exposes runtime state. lexigram system diagnoses the environment. lexigram contrib discovers CLI extensions.

Configuration

lexigram config show                        # Resolved config (secrets masked)
lexigram config show --reveal-secrets       # Unmasked
lexigram config show --format json          # yaml | json | table
lexigram config init                        # Write starter application.yaml
lexigram config validate                    # Schema + cross-field validation
lexigram config doctor --env production     # Diagnostics (--fix to auto-repair)
lexigram config env                         # Show ${VAR} references and status
lexigram config env --missing               # Only missing variables
lexigram config env-example                 # Generate .env.example
lexigram config diff --baseline a.yaml --compare b.yaml
lexigram config schema                      # Dump JSON schema

Runtime Inspection

lexigram inspect providers                  # Registered providers + priority (-v)
lexigram inspect routes                     # HTTP + GraphQL routes (-m filters method)
lexigram inspect middleware                 # Middleware stack order
lexigram inspect container                  # DI registrations (--scope filter)
lexigram inspect dependencies               # Provider dependency graph
lexigram inspect config                     # Alias for `config show`

inspect events, inspect tasks, inspect modules, and inspect health exist but print "not yet implemented" — they need runtime introspection infrastructure.

System Diagnostics

lexigram system info                        # Python, platform, config path
lexigram system health --strict             # Project + contributor checks
lexigram system doctor --fix                # Diagnostics with auto-fix
lexigram system providers                   # Provider sections in YAML
lexigram shell                              # Interactive REPL with app context (top-level)

Contributors

lexigram contrib list                       # All contributors + their surface
lexigram contrib inspect sql               # Details for one contributor
lexigram contrib check                      # Verify all load without errors

Global Flags

Flag	Effect
`--json`	Machine-readable output
`-q / --quiet`	Suppress non-essential output
`--debug`	Print tracebacks
`--no-color`	Disable ANSI
`-c / --config`	Path to `application.yaml`

Common Mistakes

Relying on stub subcommands (inspect events|tasks|modules|health) — they print "not yet implemented"
Using config show --reveal-secrets in CI logs — secrets leak
Running config validate with missing env vars — config may be valid but incomplete
Not using --json for programmatic consumption — human-friendly output is fragile to parse

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free