DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to turn repeated agent prompts into slash commands with CLI Faq Shortcuts

Install the skill, find the requests you repeat, and save each one as a short slash command.

Credentials. Prompt history can contain names, emails and tokens, and the agent may send prompts to its model provider, so review settings before use.

Who it is forA developer who retypes the same long request to a coding agent every day in one project.

The problemLong repeated requests cost typing time and get worded differently each session, so results vary.

The outcomeYour most repeated asks become named shortcuts in the project, such as /signups or /sent, stored as SKILL.md files your team can share.

What you need first

  • git and Python 3.9+ installed (macOS, Linux, or Windows with the PowerShell steps)
  • Claude Code, Codex or Cursor installed, with existing prompt history on the machine
  • A project folder you have already worked in with one of those agents

Steps

  1. Run git clone https://github.com/kishormorol/cli-faq-shortcuts ~/.agents/skills/faq-shortcuts
  2. Run mkdir -p ~/.claude/skills && ln -sfn ~/.agents/skills/faq-shortcuts ~/.claude/skills/faq-shortcuts
  3. Open your project in Claude Code, Codex or Cursor in a new session.
  4. Ask "what do I keep asking in this project?" or type /faq-shortcuts in Claude Code.
  5. Pick the asks you want. They are written as shortcuts in that project.

Prompt for your agent

In the cli-faq-shortcuts repo, install the faq-shortcuts skill as described in its Quick start, then run /faq-shortcuts in the project at <project_path>. Expected output: a table of repeated asks with how often each was typed. Verify that each chosen shortcut has a SKILL.md under .claude/skills/ in that project.

Caveat. The skill only sees history still stored on your machine, and Cursor chats opened without a folder are skipped.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page