Automated summary
This skill runs the Agentuity CLI command `auth org current` to display the default organization currently tied to the authenticated credentials.
Strengths
- Single, fast, read-only command with no side effects
- JSON output available via `--json` for scripting
- Tool scope restricted to `Bash(agentuity:*)`, limiting what the skill can do
Limitations
- Only works if the Agentuity CLI is installed and a user is already authenticated
- Cannot switch organizations or manage other credentials
- Depends on the Agentuity service and package version 0.1.24
Use it to quickly confirm which Agentuity organization subsequent commands will target.
Avoid it when you need to change the default organization or log in, since the command is strictly read-only.
Security analysis
SafeThe skill only documents a read-only Agentuity CLI command to display the current default organization, with no destructive actions, credential exfiltration, obfuscation, or safety-disabling instructions.
No concerns found
How this analysis is madeExamples
Which Agentuity organization am I currently using by default?Run the Agentuity CLI to print my current default organization in JSON format so I can parse it.name: agentuity-cli-auth-org-current description: Show the current default organization. Use for managing authentication credentials version: "0.1.24" license: Apache-2.0 allowed-tools: "Bash(agentuity:*)" metadata: command: "agentuity auth org current" tags: "read-only fast"
Auth Org Current
Show the current default organization
Usage
agentuity auth org current
Examples
Show default organization:
bunx @agentuity/cli auth org current
Show output in JSON format:
bunx @agentuity/cli auth org current --json
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/show-current-default-organization-mryiqghr/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/show-current-default-organization-mryiqghr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/show-current-default-organization-mryiqghr/download' --output '.skill-downloads/show-current-default-organization-mryiqghr/SKILL.md.part' && mv '.skill-downloads/show-current-default-organization-mryiqghr/SKILL.md.part' '.skill-downloads/show-current-default-organization-mryiqghr/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.
Tools declared by the author (check availability in your agent): Bash(agentuity:*)
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/show-current-default-organization-mryiqghr/SKILL.md' && test -s '.skill-downloads/show-current-default-organization-mryiqghr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/agentuity-cli-auth-org-current' && cp -R '.skill-downloads/show-current-default-organization-mryiqghr' '.claude/skills/agentuity-cli-auth-org-current'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/show-current-default-organization-mryiqghr'openskills read 'show-current-default-organization-mryiqghr'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/show-current-default-organization-mryiqghr/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.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.