Elastolink Meeting Skills

What to consider before installing: - This skill runs local Node.js scripts (mcp-call.cjs, get-token.cjs, set-token.cjs). Ensure Node.js is available on the machine where the agent will run (metadata does not list this requirement). - The skill reads and writes a token at D:\workspace\demo\elastolink\.env and a session file at D:\workspace\demo\elastolink\.session. Confirm you are comfortable storing the ELASTOLINK_TOKEN in plaintext at that path and that the agent process has appropriate file permissions. - The token will be sent as Authorization: Bearer <token> to dev.ideasprite.com/mcp. Only install if you trust that endpoint and the operator behind it. - The SKILL.md and scripts use absolute Windows paths; on non-Windows systems or different project locations the scripts will fail or need editing. Consider editing SKILL.md/scripts to use relative paths or an environment variable for the project path. - Source metadata is limited (registry source unknown); package.json references a GitHub URL — verify the upstream repository and maintainer if provenance matters to you. - If you want stricter handling of secrets, modify the scripts to avoid plain-file storage (use OS keyring, scoped environment variables, or explicit user prompt each session) before installing. Overall, the skill appears internally consistent with its stated function and contains no signs of obfuscated or unrelated behavior, but exercise the usual caution around storing and transmitting API tokens and ensure Node.js and correct file paths are present.