← Back to Skills Marketplace
Uplo Nonprofit
by
RooJenkins
· GitHub ↗
· v1.0.0
· MIT-0
128
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install uplo-nonprofit
Description
AI-powered nonprofit knowledge management. Search grant documentation, donor records, program reports, and compliance data with structured extraction.
Usage Guidance
Before installing: 1) Confirm provenance — the skill.json references an npm package (@agentdocs1/mcp-server) that will be fetched via npx; verify that package on the npm registry and confirm the publisher is trusted. 2) Expect to provide an agentdocs_url and an API key — only supply an API key scoped with least privilege and not a broad or admin token. 3) Because the registry metadata omitted required config, treat the manifest as incomplete and verify all required config/permissions before use. 4) Review privacy and compliance: the skill will surface donor PII and financial/compliance documents—ensure access controls, logging, and data handling meet your legal and policy requirements. 5) If you cannot validate the external npm package or vendor, run the skill in an isolated sandbox environment first, and rotate any keys after testing. If you need more certainty, ask the publisher for a signed release, clear provenance, or a vetted install artifact that you can audit offline.
Capability Analysis
Type: OpenClaw Skill
Name: uplo-nonprofit
Version: 1.0.0
The uplo-nonprofit skill is a legitimate knowledge management tool designed for nonprofit organizations to manage grants, donor records, and compliance data. It utilizes a standard MCP server architecture via the @agentdocs1/mcp-server package and provides well-documented tools for structured data extraction and search. The instructions in SKILL.md and identity-patch.md are aligned with the stated purpose and include explicit directives for the agent to respect data confidentiality and avoid fabrication.
Capability Assessment
Purpose & Capability
Name, README, SKILL.md, and identity-patch all describe nonprofit knowledge management and list tools (search_knowledge, search_with_context, export_org_context, get_directives) that match that purpose. However, registry metadata reported 'Required env vars: none' while skill.json declares required configuration (agentdocs_url and api_key). That mismatch reduces confidence in the package metadata.
Instruction Scope
SKILL.md only instructs the agent to call MCP tools (use_mcp_tool: search_knowledge, search_with_context, get_directives, etc.) and to respect classification tiers. It does not instruct the agent to read arbitrary local files or unrelated environment variables, nor to send data to endpoints outside the configured UPLO/agentdocs MCP server. Scope of instructions is consistent with the stated purpose.
Install Mechanism
The skill is instruction-only in the registry, but README and skill.json show an implicit runtime install using `npx -y @agentdocs1/mcp-server` (and the README suggests a 'clawhub install'). That means code will be fetched from the npm registry at runtime; this is a moderate-risk install mechanism because arbitrary package contents will be downloaded and executed locally. The registry did not include an explicit install spec, which is an inconsistency and reduces auditability.
Credentials
The functionality reasonably requires an UPLO instance URL and an API token (agentdocs_url and api_key in skill.json). That credential request is proportionate to the purpose. However, the registry metadata advertised 'none' for required env/config, while skill.json requires these two config entries (api_key is secret). The discrepancy is a coherence problem and could mislead administrators about what secrets they must provide.
Persistence & Privilege
The skill does not request always:true, does not declare system-wide config paths, and is user-invocable only. It does require network access to the configured MCP server, but that is reasonable for a remote knowledge-service integration and does not request elevated or permanent platform privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install uplo-nonprofit - After installation, invoke the skill by name or use
/uplo-nonprofit - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release offering AI-powered nonprofit knowledge management.
- Search and extract structured data from grant documents, donor records, program reports, and compliance files.
- Tools support tasks like grant writing, board reporting, fund tracking, audit response, and onboarding.
- Structured queries return metrics (e.g., outcomes, financials) in usable formats for reports and applications.
- Highlights nonprofit-specific features: logic models, funding source tracking, and organizational context export.
- Helps identify missing documentation and ensure strategic alignment with board-approved priorities.
Metadata
Frequently Asked Questions
What is Uplo Nonprofit?
AI-powered nonprofit knowledge management. Search grant documentation, donor records, program reports, and compliance data with structured extraction. It is an AI Agent Skill for Claude Code / OpenClaw, with 128 downloads so far.
How do I install Uplo Nonprofit?
Run "/install uplo-nonprofit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Uplo Nonprofit free?
Yes, Uplo Nonprofit is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Uplo Nonprofit support?
Uplo Nonprofit is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Uplo Nonprofit?
It is built and maintained by RooJenkins (@roojenkins); the current version is v1.0.0.
More Skills