Stakeholder briefer
Skill AtulPurohit/Antigravity-Awesome-Skills/skills/stakeholder-briefer
Professional Stakeholder Briefer Expert skill. Orchestrate technical collaboration, design reviews, sprint planning, and system diagnostics.From its SKILL.md
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill stakeholder-brieferAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 180 tokens by cl100k_base, as published. Nobody here has run it
Stakeholder Briefer Expert
Purpose
Manage and implement Stakeholder Briefer Expert requirements efficiently within enterprise applications.
Core Concepts
Detailed operational framework for Stakeholder Briefer Expert:
1️⃣ Overview and Strategy
Understanding boundaries, rules, and best practices for the stakeholder-briefer feature domain.
2️⃣ Code Implementation Reference
## Review Guidelines
- Respect coding guidelines
- Prioritize correctness and security
- Keep feedback constructive and educational
3️⃣ Checklist & Validation Rules
- Integration validation checklist completed.
- Code conventions and naming rules followed.
- Strict type safety constraints verified.
- Security standards checked.
Outputs
- System integration pattern definitions.
- Code templates and examples.
- Test validation checklists.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 180 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- respect coding guidelines
- prioritize correctness and security
- keep feedback constructive and educational
- complete integration validation checklist
- follow code conventions and naming rules
- verify strict type safety constraints
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.