no-today
- 6 skills
- 0 followers
- 12 hours ago last updated
- ▌ Use Aidev · no-todayUse when an AI agent enters a workspace and needs to discover which aidev CLIs (dbcli/logcli/jcli/apicli) are usable here, and — when a task targets one of several configured targets — which CLIs apply to that target. `aidev` is a read-only discovery command scoped to the workspace's active scene. Also the shared-setup reference — first-time configuration of `~/.aidev-clis` (config-dir layout, the credentials model, the copy-a-template-and-fill workflow) and config backup/restore.
- ▌ Aidev Jcli · no-todayUse when an AI agent needs to trigger or watch a Jenkins build, deploy a service, check build status, tail a build log, cancel a build, or discover jobs/parameters — across configured Jenkins instances. Covers the service-centric model, the configurable deploy flow, the JSON envelope, and target-based discovery.
- ▌
- ▌ Aidev Dbcli · no-todayUse when an AI agent needs to read (or, with explicit intent, write) a database — running SQL, listing databases/tables/columns, diagnosing locks, or checking connectivity — across configured targets (mysql / postgres / kingbase / redis / sqlite / mongo; plus dataease, a last-resort read-only HTTP bypass). Covers the read/write guard, the JSON envelope, the namespace model, and target inference.
- ▌ Aidev Apicli · no-todayUse when managing aidev HTTP session state or making HTTP calls with apicli login (capture a session via a flow), apicli whoami (inspect current session), apicli logout (remove session file), or apicli call (send HTTP request with injected session). Covers verb-first addressing, auto-login + auto-relogin (call is self-sufficient — no login-first), the {data}/{error} envelope, per-app response predicates, actors (incl. secret:<name>), and flow fidelity — multi-step + cross-step capture, per-step assert, cookie_from_set_cookie, multi-header inject, vars_defaults, extra_headers, trace_field, and file downloads (--output-file).
- ▌ Aidev Logcli · no-todayUse when an AI agent needs to read logs — listing what's tailable (apps/containers/files/logstores), fetching a bounded slice of logs, following live (-f / tail), searching, or tracing a request across services — from kubectl, docker, SSH hosts, local files, or Aliyun SLS, across configured targets.