← Back to Skills Marketplace
Maven Smart System Ai (palantir integration)
by
Alexey Mametyev
· GitHub ↗
· v1.0.1
· MIT-0
277
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install palantir-integration
Description
Advanced text-based integration suite for Palantir Maven Smart System (MSS). Manages targets, Kanban workflow, CDE risk assessment, SIGINT intelligence fusio...
Usage Guidance
This package contains real-world targeting functionality and will call your Palantir MSS endpoint using MSS_API_KEY and MSS_API_ENDPOINT. Before installing: 1) Verify the publisher and source — there is no homepage or known owner. 2) Do not provide a high-privilege/production API key for testing; create a least-privilege, audit-enabled test key instead. 3) Inspect the code locally (mss_client.py, setup_env.py, and the POST/PATCH callers) and confirm you trust the endpoint URL; setup_env.py writes credentials in plaintext to a .env at the repo root and can overwrite existing MSS entries. 4) Ensure your agent runtime enforces the SKILL.md safety confirmations (the scripts themselves will execute actions if invoked). 5) If you need stronger assurance, request provenance (signed release, VCS repo, maintainer identity) or run the skill in an isolated environment without network access until validated.
Capability Analysis
Type: OpenClaw Skill
Name: palantir-integration
Version: 1.0.1
The skill bundle provides a functional integration for a tactical management system (Palantir MSS). The Python scripts are standard API wrappers using the 'requests' library, and the configuration process in 'setup_env.py' correctly handles secrets via a local .env file. Most importantly, the 'SKILL.md' instructions include a mandatory safety protocol requiring explicit operator confirmation for high-risk actions like strike assignments, and there are no signs of data exfiltration, obfuscation, or malicious command execution.
Capability Assessment
Purpose & Capability
The SKILL.md and bundled scripts clearly implement Palantir MSS functionality (target lookup, SIGINT fetch, CDE, assigning strike assets, status changes). That matches the declared purpose. However, the registry metadata at the top of the submission lists 'Required env vars: none' and 'Primary credential: none', while SKILL.md and the code require MSS_API_KEY and MSS_API_ENDPOINT — an important metadata mismatch that could hide required credentials from reviewers.
Instruction Scope
SKILL.md instructs the agent to check for MSS_API_KEY and to call initialize_config to write a .env file if missing; it also requires explicit operator confirmation (per the 'Safety Protocol') before actions that move targets toward engagement. This scope is consistent with the stated purpose. However, confirmation is a procedural requirement in SKILL.md only — it is not enforced by the scripts themselves (the scripts will perform POST/PATCH calls if invoked). The agent runtime must reliably prompt and block potentially harmful actions; otherwise the skill can perform impactful operations.
Install Mechanism
No external install script or remote download is present; the package is instruction+scripts only. requirements.txt lists common Python libs (requests, python-dotenv). No high-risk remote installs or obscure URLs were found.
Credentials
SKILL.md and mss_client.py legitimately require MSS_API_KEY and MSS_API_ENDPOINT. But the registry metadata omitted these required env vars — an incoherence. The setup_env.py writes the API key and endpoint into a plaintext .env file at the repository root, which will persist sensitive credentials on disk and may overwrite or alter an existing .env; this persistence is disproportionate unless the operator expects local storage. No other unrelated credentials are requested.
Persistence & Privilege
The skill does not request 'always: true' or other elevated platform privileges. It does, however, persistently store the API key and endpoint in a .env file and will make authenticated API calls (GET/POST/PATCH) to the configured endpoint. That persistent storage is normal for a client integration but increases the blast radius if the workspace is shared or backups/uploaded.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install palantir-integration - After installation, invoke the skill by name or use
/palantir-integration - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
**Major release with expanded tactical integration capabilities and strict response protocols.**
- Upgraded from "palantir-integration" to "Maven-Tactical-Link" (version 2.0.0) with a broader feature set.
- Introduces advanced tools for risk assessment, SIGINT fusion, asset assignment, strike logistics, and more.
- Enforces concise, structured, military-style text reporting—no graphical output.
- Adds explicit confirmation requirements for strike-related actions to ensure safety.
- Implements strict error transparency: all script errors are shown verbatim.
- Defines a standard tactical report format and multi-tool workflow for full target briefings.
Metadata
Frequently Asked Questions
What is Maven Smart System Ai (palantir integration)?
Advanced text-based integration suite for Palantir Maven Smart System (MSS). Manages targets, Kanban workflow, CDE risk assessment, SIGINT intelligence fusio... It is an AI Agent Skill for Claude Code / OpenClaw, with 277 downloads so far.
How do I install Maven Smart System Ai (palantir integration)?
Run "/install palantir-integration" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Maven Smart System Ai (palantir integration) free?
Yes, Maven Smart System Ai (palantir integration) is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Maven Smart System Ai (palantir integration) support?
Maven Smart System Ai (palantir integration) is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Maven Smart System Ai (palantir integration)?
It is built and maintained by Alexey Mametyev (@frequensy23-coder); the current version is v1.0.1.
More Skills