GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Proposal: FeathersJS Agent Skill and potential official repo · Issue #3670 · feathersjs/feathers

Proposal: FeathersJS Agent Skill and potential official repo #3670

New issue
Copy link
New issue
Copy link
Open
Open
Proposal: FeathersJS Agent Skill and potential official repo#3670
Copy link

Description

@nazifishrak
nazifishrak
opened on Mar 14, 2026
Issue body actions

Hi there 👋

I’ve been working on an Agent Skill for FeathersJS and wanted to share it, and also ask if you’d be open to having an official repo for it under the Feathers organization.

Right now the skill lives in my personal repo and can be installed with:

npx skills add nazifishrak/feathersjs-expert-skill

Image

When you run this inside a project, it installs a folder with markdown files and references that agents can read to understand Feathers best practices, patterns, and implementation details. Most editor agents that support Agent Skills handle the orchestration on their side.

You can read more about the Agent Skills format here: https://agentskills.io/home

It would be nice if, long term, there was an official FeathersJS repo so people could use an official prefix instead of my personal one (for example, something like ‎feathersjs/feathers-expert-skill or whatever naming you prefer). That would also make it easier for the community to contribute and keep the skill up to date.

The current skill content is based on the docs from the v6 branch. There are a few references to v5 in the markdown files, so there’s some back and forth between v5 and v6 right now. These can be consolidated and cleaned up over time as v6 evolves and stabilizes more. There’s also a skill that helps modify existing Agent Skills, which should make maintenance and evolution easier.

Hope this helps the feathersjs community!

Activity

  1. nazifishrak commented on Mar 14, 2026

    @nazifishrak
    nazifishrak
    on Mar 14, 2026
    Author
    More actions

    @daffl @marshallswain

  2. daffl commented on Mar 19, 2026

    @daffl
    daffl
    on Mar 19, 2026
    Member
    More actions

    This is great, thank you for putting that together! I've been debating of generating an llms.txt from those same API docs, would that even still be necessary in this case? Also, do you know how this handles updates?

  3. nazifishrak commented on Mar 20, 2026

    @nazifishrak
    nazifishrak
    on Mar 20, 2026
    Author
    More actions

    I think LLMs.txt is primarily meant to be read by crawlers/AI tools at training time and indexing time, and sometimes again at inference time when a tool wants to explicitly read a website. But the agent skills are used by the agent while working on the project during inference time and is more flexible as you can make it point to using other skills or tools etc. So LLMs.txt would live in a different layer than an agent skill and the agents in most editors handle iterative orchestration while using a skill which wouldn't be possible if you just gave a flat llms.txt with the repo as the agent wouldn't automatically pick it up efficiently. For e.g you can look at the nestjs skill
    There is already a skill used to develop and maintain/improve a skill which can be used to maintain a skill easily.

  4. daffl commented on Mar 24, 2026

    @daffl
    daffl
    on Mar 24, 2026
    Member
    More actions

    Great, thank you for the clarification. I am working on finishing up the v6 docs. Would be great to test this again once they are done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.