Skip to content

Rename to flutter/agent-plugins#171

Merged
kenzieschmoll merged 3 commits into
mainfrom
rename-to-agent-plugins
Jul 13, 2026
Merged

Rename to flutter/agent-plugins#171
kenzieschmoll merged 3 commits into
mainfrom
rename-to-agent-plugins

Conversation

@johnpryan

@johnpryan johnpryan commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

This updates the README and any references to flutter/skills to point to flutter/agent-plugins.

Once this lands, I will rename the repo.

The website docs are being updated here: flutter/website#13568

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request rebrands the repository and its components from 'Flutter Agent Skills' to 'Flutter Agent Plugins'. It updates documentation, installation scripts, configuration files, and tests to replace references to the old repository name (flutter/skills) with the new one (flutter/agent-plugins), while also clarifying the relationship between plugins and skills in the README. I have no feedback to provide as there are no review comments.

Comment thread README.md Outdated
Agent plugins for Flutter, maintained by the Flutter team.

Skills are essentially simple folders of files that can be seen as complementary to MCP, where MCP gives an agent access to specialized tools and a Skill teaches the agent “how” to use tools for a specific task.
A collection of plugins designed to extend AI agent capabilities for Flutter development. These plugins bundle together skills, subagents, rules, and configurations to provide tailored workflows and instructions for happy path Flutter development. By giving the agent domain expertise and repeatable workflows, you drastically reduce mistakes and ensure agents reliably complete tasks following best practices.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should the MCP server be mentioned here?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it should be mentioned.

Comment thread README.md Outdated
You can also install the [Agent Skills for Dart](https://github.com/dart-lang/skills) for Dart tasks.
Plugins can package various customizations together. A key component of these plugins is **Agent Skills**, which are simple folders of files that can be seen as complementary to MCP: where MCP gives an agent access to specialized tools, a Skill teaches the agent “how” to use tools for a specific task.

You can also install the [Agent Plugins for Dart](https://github.com/dart-lang/skills) for Dart tasks.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this link actually be pointing to "skills" instead of "agent plugins for dart"?

Comment thread README.md
Comment on lines +13 to +18
To install the plugins into your project, run the following command.
The `--agent universal` flag puts them in the standard `.agents/skills`
folder that most agents use.

```bash
npx skills add flutter/skills --skill '*' --agent universal --yes
npx skills add flutter/agent-plugins --skill '*' --agent universal --yes

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks incorrect and the whole section should probably be rewritten to have install steps for each plugin. And for standalone skill install via npx skills (and eventually through package:skills)

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we're ready to publish installation instructions for plugins. We have sort of a chicken-and-the-egg problem here. If we don't make this change, we can't publish the plugins from the right repo, and if we add the plugin instructions first, users won't be able to follow them, because they haven't been published yet.

Comment thread README.md
```

## Updating Skills
## Updating Plugins

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this section is probably also obsolete now and needs to be updated

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a updating plugins section? AFAIK, the agent updates the plugins when there are new releases.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above, I think we need to circle back and update these again once we publish the plugins to the various marketplaces.

Updated README to specify MCP server configuration in plugins description.

@kenzieschmoll kenzieschmoll left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine to land this as is and do another iteration on docs once we have the plugins published.

@kenzieschmoll kenzieschmoll merged commit 21f3da3 into main Jul 13, 2026
14 checks passed
@kenzieschmoll kenzieschmoll deleted the rename-to-agent-plugins branch July 13, 2026 16:48
lamek pushed a commit to flutter/website that referenced this pull request Jul 13, 2026
This updates references to flutter/skills to point to
flutter/agent-plugins. We are repurposing this repo to enable publishing
agent plugins, which will include MCP config, skills, rules, hooks, etc.

Depends on flutter/agent-plugins#171 landing before we
can land this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants