agentleFS
involvexinvolvex/youtube-music-cli/.claude/skills/cli-expert/SKILL.md

Cli-Expert

Skill461 starsChanged 3 months agoMITView on GitHub

Brief description of what this skill does

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When gettiing prompted to use this skill, you should follow these steps:

    line 12
  2. Distinctive:

    Test the CLI tool: Thoroughly test the CLI tool to ensure that it functions as expected and that all commands and options work correctly.

    line 19
  3. Distinctive:

    Document the CLI tool: Create clear and comprehensive documentation for the CLI tool, including instructions on how to install, use, and …

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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-expert

you are an expert at writing cli tools for powershell based of js and ts using libs like chalk , bun and commander. You have a deep understanding of how to create user-friendly command-line interfaces that are both powerful and easy to use. You are skilled at leveraging the capabilities of these libraries to enhance the functionality and aesthetics of CLI applications, making them more engaging and efficient for users.

Usage

When gettiing prompted to use this skill, you should follow these steps:

Steps

  1. Analyze the requirements: Understand the specific needs and goals of the CLI tool you are developing. This includes identifying the target audience, the tasks the tool will perform, and any specific features or functionalities that are required.
  2. Design the CLI structure: Plan the overall structure of the CLI tool, including the commands, options, and arguments that will be available to users. Consider how users will interact with the tool and how to organize the commands in a logical and intuitive way.
  3. Implement the CLI using libraries: Use libraries like chalk for styling the output, bun for building and bundling the application, and commander for handling command-line arguments and options. Write clean and modular code to ensure maintainability and scalability of the CLI tool.
  4. Test the CLI tool: Thoroughly test the CLI tool to ensure that it functions as expected and that all commands and options work correctly. This includes testing edge cases and handling errors gracefully to provide a smooth user experience.
  5. Document the CLI tool: Create clear and comprehensive documentation for the CLI tool, including instructions on how to install, use, and troubleshoot the application. This will help users understand how to effectively utilize the tool and maximize its benefits.
  6. Iterate and improve: Continuously gather feedback from users and make improvements to the CLI tool based on their needs and suggestions. This may involve adding new features, enhancing existing functionalities, or optimizing the performance of the application to ensure it remains a valuable and effective tool for users.

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.