Marriage Matching
v1.0.0Generates bride and groom horoscopes then produces a marriage compatibility report with PDF outputs.
⭐ 0· 29·0 current·0 all-time
byToolWeb@krishnakumarmahadevan-cmd
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (marriage matching, horoscopes, PDF reports) match the SKILL.md and openapi.json endpoints. No unrelated credentials, binaries, or installers are requested.
Instruction Scope
Instructions and OpenAPI describe submitting bride/groom personal and birth data to an external API (search-city, /api/seek-alliance, downloads). This is consistent with the stated purpose, but the skill will transmit sensitive PII (names, parents' names, DOB/time, mobile, birth place) to api.mkkpro.com (no homepage or owner info provided in the package).
Install Mechanism
No install spec and no code files—this is instruction-only. No archives or external installers are pulled, so there is no on-disk installation risk from the skill bundle itself.
Credentials
No environment variables, credentials, or config paths are requested, which is appropriate. However, the API requires submission of sensitive personal data; absence of declared auth or privacy metadata means data handling is opaque and should be verified with the service owner.
Persistence & Privilege
Default privileges (always=false, agent-invocable allowed) are used. The skill does not request persistent/privileged platform presence or modifications to other skills.
Assessment
This skill is internally consistent for generating astrological reports, but it submits sensitive PII (names, parents' names, DOB/time, mobile, birthplace) to an external API host (api.mkkpro.com) and the package provides no homepage or source attribution. Before installing or using it with real data: verify the API owner's identity and privacy/data-retention policies; prefer a service with documented TLS, authentication, and GDPR/India-data protections; test with synthetic or redacted data first; and don't provide platform-wide credentials since none are required by the skill. If you cannot verify the service, avoid sending real personal data.Like a lobster shell, security has layers — review code before you run it.
latestvk971pgbms42mnpy87geay95fy9849mzp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
