Inspect the host running the AgentOS process, including its operating system, architecture, Python runtime, processor, and UTC time. You can also list the direct contents of a chosen directory, with the skill folder as the default location.
Inspect the host operating system, Python runtime, and local files
Run score Not tested
See how to installThe system-info skill checks the host where the AgentOS process is running. The included get_system_info.py script returns the hostname, operating system, architecture, Python version and executable, processor, and current UTC time. The list_directory.py script lists the direct contents of a specified directory. If you omit the path, it uses the skill’s directory.
Use it when you need details about the environment running the agent or want to see which files and folders are directly inside a directory on that host. It can also provide runtime results to answer questions about the host environment.
The scripts must be run through the skill tool. Use standard output only when the exit code is 0. For other exit codes, report the standard error or JSON error instead of inferring the result.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 25, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Use this skill when the user asks about the host running the AgentOS process or needs a directory inventory from that host.
get_system_info.py returns the hostname, operating system, architecture,
Python version and executable, processor, and current UTC time.list_directory.py lists the direct children of a directory. It accepts one
optional path argument and defaults to the skill directory.Load these instructions before choosing a script. Execute a script through the skill tool and inspect its structured result:
get_skill_script(
skill_name="system-info",
script_path="get_system_info.py",
execute=True,
)
To list a directory:
get_skill_script(
skill_name="system-info",
script_path="list_directory.py",
execute=True,
args=["."],
)
Only use data parsed from stdout when returncode is 0. If execution
returns a nonzero code, report stderr or the JSON error instead of inferring
the result.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Reviews code for style, naming, error handling, exposed credentials, and possible bugs, security, or performance issues. It can run an automated style check and returns structured feedback grouped by severity, from critical fixes to optional improvements.
Get practical guidance for Git commits, branch names, and pull requests. The skill follows a consistent commit format, offers naming patterns and a PR description template, and includes common commands for starting, updating, and submitting work.
Reviews configured sources and proposes actionable backlog tasks tied to a suitable project. Each proposal cites inspected evidence and its observed content hash, while stable keys prevent duplicate proposals across later scans.
Refreshes a product’s status using its playbook, projects, tasks, and configured sources. It records observed progress and failures, removes references to archived work, and presents project completion proposals for human review without changing task or project states.
Summarizes a Product’s recorded changes, pending owner actions, and failures since the last successful delivery. It writes the report to the configured wiki and sends it through the configured interface, or records a quiet check when nothing needs attention.