Notion Sync Obsidian

This skill appears to implement a legitimate Notion→Obsidian sync, but there are a few things to check before installing: - Metadata mismatch: the registry claims no credentials required but the skill requires a Notion API token (api_key) in config.json. Expect to supply a long-lived Notion integration token and store it in the skill's config file. - Secret handling: the scripts print and log API-related info (they display the first 10 chars of the API key and user/workspace names). Ensure the skill directory and log files (sync_timer.log) are protected (filesystem permissions) and not world-readable; consider removing the token after testing or using a least-privilege integration. - Persistence: the skill launches a background process (nohup timer_checker.sh) and creates sync_timer.pid and sync_timer.log. Be prepared to manage/stop that process and review the log contents regularly. - Code review: you can reasonably inspect the shipped scripts (they are plain shell/Python). The visible code only calls Notion API endpoints and writes to local disk — there are no hidden external endpoints in the provided files. However part of real_notion_checker.py was truncated in the provided listing; verify the rest of that file before trusting it fully to ensure it doesn't perform unexpected network calls or upload data elsewhere. - Run in a safe environment first: if you're cautious, run the skill in a confined environment (container or dedicated user account) and use a Notion integration with minimal permissions. If these checks are acceptable, the skill seems coherent with its stated purpose. If you need the registry to reflect required credentials, ask the maintainer to declare the Notion API key requirement in the skill metadata.