agentleFS
itseffiitseffi/agentic-os/.agents/skills/hidden-agendas/SKILL.md

hidden-agendas

Skill114 starsChanged 10 months agoMITView on GitHub

Identify potential hidden agendas of stakeholders. Use before high-stakes meetings with complex motivations.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Before high-stakes meetings where stakeholder motivations may be complex.

    line 12
  2. Distinctive:

    Consider for each stakeholder:

    line 16
  3. Distinctive:

    Document their official position

    line 47
  4. Distinctive:

    Consider how agendas might interact or conflict

    line 50
  5. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 71

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

Hidden Agenda Analysis

Identify potential hidden agendas of stakeholders before important meetings.

When to Use

Before high-stakes meetings where stakeholder motivations may be complex.

Analysis Factors

Consider for each stakeholder:

Official Position

  • Their stated role/stance

Potential Interests

  • Financial interests
  • Power dynamics
  • Reputation management
  • Career advancement
  • Ideological beliefs
  • Personal relationships
  • Organizational politics

Historical Context

  • Past behaviors
  • Previous positions
  • Track record

Relationships

  • Alliances with other stakeholders
  • Conflicts or tensions
  • Dependencies

Outcome Analysis

  • What do they gain from different outcomes?
  • What do they lose?

The Process

  1. List all stakeholders involved
  2. Document their official position
  3. Analyze potential hidden motivations
  4. Identify supporting factors for your analysis
  5. Consider how agendas might interact or conflict

Output Format

For each stakeholder:

  • Name
  • Official position
  • Potential hidden agenda
  • Supporting factors

Plus: Overall situation summary showing how agendas interact.

Principles

  • Base analysis on provided information and reasonable inference
  • Avoid unfounded speculation
  • Consider multiple possibilities
  • Stay objective and impartial

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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.