Skip to content

Please adhere to a better skills standard #204

Description

@Rykarix

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions