Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Please adhere to a better skills standard

Open
  • Is something wrong?
#204 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown
Domain
cli, documentation, tooling

Research direction

The issue names no repository files or tests; start by inventorying the current 33 skills and the existing firecrawl-cli skill layout, then compare the proposed SKILL.md and references structure with agentskills.io. Done means redundant per-harness skills are consolidated, references cover the documented commands, and any recommender behavior is specified and tested.

Written by the indexing model from the issue text.

Description

firecrawl-cli is a single tool and therefore it should NOT require 33 skills.

This adds a huge amount of redundant crap into the context window of every user submitted message. Additionally it's incredibly annoying and messy having a tool that just spams files and folders all over the ~ directory for every harness you support.

Using a tool should be only a single skill and you should follow a better standard.

A SKILL.md should represent the 4 W's:

  • What
  • Where
  • When
  • Why

The references should contain the how

Please create a single skills (firecrawl-cli) and structure it like this:

---
name: firecrawl-cli
description: ...
allowed-tools:
  - Bash(firecrawl *)
  - Bash(npx firecrawl-cli *)
metadata:
  - last-updated: X
---
<overview>

TheFirecrawl CLI enables easy interaction with the web.

</overview>

<references>
<!-- Remember: what | where | when | why -->
- [firecrawl search {query}](./references/firecrawl-search.md)
   - Use When:
      - Url Unknown, finding sources, articles or news.
   - Not When:
      - Research papers: `firecrawl research index *` better
      - Software development (libs, api, error, bugs, etc): `firecrawl developer index *` better
- ...etc
</references>

Better yet, create a simple recommender system that the agent can use via the cli. Like firecrawl skill recommender *query for eg: firecrawl skill recommender "firecrawl api search executeSearch command" would return [firecrawl developer](./references/firecrawl-developer-index.md) and [firecrawl search](./references/firecrawl-search.md)

Either way, please stop creating N^10 skills for a single product.

Useful refs for you to check out:

Thanks

Dominant language
TypeScript
Stars
643
Forks
110
Avg merge
4h 16m
Merged PRs (30d)
48

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firecrawl/cli

All issues in firecrawl/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.