mcpbeat

Package Info

microsoft/package-info

Quick lookup for a Fluent UI package — path, dependencies, owner team, Nx project details, and relevant docs

505 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
20188
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/fluentui --skill package-info

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

4 sections, as written by the author

Package Info Lookup

Get a comprehensive overview of the package $ARGUMENTS.

Steps

  • Resolve the package path. Map the name to a filesystem path:
  • react-button or @fluentui/react-button → packages/react-components/react-button/
  • Check both library/ (source) and stories/ (storybook) sub-packages
  • Get Nx project details:
   yarn nx show project @fluentui/$ARGUMENTS --json 2>/dev/null || yarn nx show project $ARGUMENTS --json 2>/dev/null
  • Read the package.json for version, dependencies, and peer dependencies.
  • Check ownership by searching CODEOWNERS:
   grep -i "$ARGUMENTS" CODEOWNERS
  • Summarize the component structure — list files under library/src/components/.
  • Check test coverage — does it have:
  • Unit tests (*.test.tsx)
  • Conformance tests (testing/isConformant.ts)
  • Stories (stories/ package)
  • Report in this format:
   Package: @fluentui/<name>
   Path: packages/react-components/<name>/library/
   Version: x.y.z
   Tier: 3 (Component) | 2 (Foundation) | 1 (Core)
   Owner: <team from CODEOWNERS>
   Dependencies: <list relevant @fluentui deps>
   Components: <list exported components>
   Tests: unit ✓/✗ | conformance ✓/✗ | stories ✓/✗

Useful Commands for the Package

yarn nx run <project>:build          # Build
yarn nx run <project>:test           # Unit tests
yarn nx run <project>:lint           # Lint
yarn nx run <project>:type-check     # Type check
yarn nx run <project>:generate-api   # Regenerate API docs (etc/*.api.md)

References

  • Package layers: docs/architecture/layers.md
  • Team routing: docs/team-routing.md

How to use it

Copy the folder

Take microsoft/package-info from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.