agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/collate-feature-asks/SKILL.md

collate-feature-asks

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Collate Feature Asks”. A useful skill states the six fields from Skills and routines. The same product request is living in many Slack threads and needs one cluster with quotes, frequency, and a suggested issue — not a roadmap decision. Every cluster has at least one link. Frequency is a count of threads, not a vibe. No commitment language ("we will…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Search the named channels for asks in the window.

    line 22
  2. Distinctive:

    Check the tracker for an existing issue.

    line 25
  3. Distinctive:

    Every cluster has at least one link.

    line 30
  4. Distinctive:

    Do not file issues, change the roadmap, or reply in Slack.

    line 40

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

Collate Feature Asks

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Collate Feature Asks”.

A useful skill states the six fields from Skills and routines.

1. When to use it

The same product request is living in many Slack threads and needs one cluster with quotes, frequency, and a suggested issue — not a roadmap decision.

2. Required inputs and access

  • Slack channels or exported threads the owner named
  • Time window
  • Existing issue tracker (to de-dupe)

3. Sequence of work

  1. Search the named channels for asks in the window.
  2. Cluster by underlying job-to-be-done, not by the requester's wording.
  3. Attach representative quotes with links.
  4. Check the tracker for an existing issue.
  5. Draft a problem statement. Do not prioritize.

4. How to validate the result

Every cluster has at least one link. Frequency is a count of threads, not a vibe. No commitment language ("we will ship").

5. What to return

Cluster table: job, count, quotes, existing issue or none, draft problem statement.

6. What requires approval

Do not file issues, change the roadmap, or reply in Slack.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.

Check your setup, free