Hone

Audit AI CLI configurations for Codex, Gemini, and Claude Code.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill hone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Hone
Source: https://github.com/simota/agent-skills/tree/main/hone
Command: npx skills add https://github.com/simota/agent-skills --skill hone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines your AI CLI experience by auditing and optimizing your Codex CLI, Gemini CLI, and Claude Code configurations against official best practices, ensuring security, efficiency, and optimal performance.

Core Features & Use Cases

  • Comprehensive Audits: Analyzes configurations for Codex, Gemini, and Claude Code.
  • Best Practice Alignment: Fetches and applies official documentation recommendations.
  • Gap Analysis & Proposals: Identifies configuration gaps and provides Before/After diffs for improvements.
  • Security & Optimization: Reviews trust levels, feature flags, permissions, and performance settings.
  • Use Case: Automatically check your ~/.codex/config.toml for outdated settings, security risks, and performance bottlenecks, receiving actionable recommendations to improve your AI CLI setup.

Quick Start

Run a full audit of your AI CLI configurations.

Frequently Asked Questions about Hone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my Claude Code and Codex CLI configurations against best practices?

To audit Claude Code and Codex CLI configurations, analyze settings, permissions, trust levels, and feature flags against official documentation to identify gaps and security risks, generating actionable Before/After diff proposals for improvement.

What is the best way to optimize AI CLI settings for security and performance?

Optimizing AI CLI settings involves reviewing trust levels and feature flags against official best practices to detect performance bottlenecks and security vulnerabilities, then applying actionable configuration diff proposals to align with documented standards.

Why does my Gemini CLI configuration have security risks or outdated settings?

Gemini CLI configurations develop security risks and outdated settings when permissions and feature flags diverge from official documentation standards, requiring a comprehensive audit to detect misconfigurations and generate corrective Before/After diffs.

Can I check my Codex config.toml file for performance bottlenecks and feature flag gaps?

Yes, you can check your Codex config.toml file by analyzing its settings and feature flags against official best practices to identify performance bottlenecks, configuration gaps, and security risks, producing actionable optimization proposals.

Do I need official documentation to generate Before/After diff proposals for AI CLI improvements?

Generating Before/After diff proposals for AI CLI improvements requires fetching and applying official documentation recommendations to analyze current trust levels and settings, ensuring the proposed configuration changes align with documented security and performance standards.