Stakeholder Management

v1.0.0

Expert in identifying, analyzing, and engaging stakeholders to align interests, reduce resistance, and ensure successful project outcomes.

0· 583·6 current·6 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description align with the SKILL.md content: templates, analyses, and engagement playbooks match a stakeholder-management skill. No unrelated binaries, env vars, or config paths are requested. Note: registry 'source' and homepage are absent; README references AfrexAI branding and context-pack links, but absence of an authoritative homepage is a provenance/credibility concern (not a functional mismatch).
Instruction Scope
The instructions stay within the stated purpose (identify, analyse, engage stakeholders). They ask the agent to collect contextual information (stakeholder names, contacts, attitudes, influence networks). That is expected, but it entails collecting personal and potentially sensitive PII about stakeholders — a privacy consideration rather than a functional incoherence. The SKILL.md does not instruct the agent to read system files, access env vars, or exfiltrate data to hidden endpoints.
Install Mechanism
No install specification and no code files — instruction-only skill. This is lowest-risk from an install perspective (nothing is written to disk or fetched during install).
Credentials
No environment variables, credentials, or config paths are required. The skill does not request unrelated secrets or tokens.
Persistence & Privilege
always is false and there is no indication the skill modifies other skills or system settings. Model invocation is enabled (default) which is normal for skills; this increases runtime autonomy but is not a red flag here given the limited scope and lack of requested credentials.
Assessment
This skill is instruction-only and internally consistent with its purpose, but consider these before installing: 1) Provenance: the publisher/homepage are not provided — verify the publisher (Af rexAI references in README) if provenance matters for your organization. 2) Privacy: the templates ask for stakeholder names, contact details, attitudes, and influence networks. Do not paste sensitive personal data, private contact information, or regulated data (e.g., health, financial) unless you have consent and appropriate data-handling controls. 3) Logs and retention: confirm how your agent/runtime stores conversation logs and whether those logs are accessible to others; avoid entering PII if logs are persisted. 4) External links: README mentions context-pack URLs; the skill itself does not auto-download code, but an agent could be instructed to fetch those links — be cautious about following or fetching external resources. 5) Enterprise use: if deploying in a corporate environment, have security/privacy teams vet the skill and its publisher. Overall: safe-to-install from a technical footprint perspective, but exercise standard privacy and provenance due diligence.

Like a lobster shell, security has layers — review code before you run it.

communicationvk973zb4xz3b2jr0rt3csf45gw18198vmlatestvk973zb4xz3b2jr0rt3csf45gw18198vmleadershipvk973zb4xz3b2jr0rt3csf45gw18198vmmanagementvk973zb4xz3b2jr0rt3csf45gw18198vmstakeholdervk973zb4xz3b2jr0rt3csf45gw18198vm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments