refly

Least-privilege permissions

• Rotate API keys regularly – Change any passwords or access tokens that skills use to connect to external services (like Slack, databases) every 30–90 days, or immediately if a skill is deleted or team member leaves.
• Limit what each skill can access – When creating a skill, grant it only the specific permissions it needs (e.g., "read messages" not "delete all messages"); audit existing skills quarterly to remove unused access.
• Use separate credentials per environment – Keep different API keys for testing, staging, and production so a leaked test key doesn't compromise live data.
• Enable multi-factor authentication (MFA) – Require MFA on any platform accounts that host or authenticate skills (GitHub, Claude Code, Slack workspace admin, etc.).

Network isolation

• Restrict outbound connections – Configure firewall or network rules so skills can only communicate with approved external services (whitelist IP addresses or domains rather than allowing all outbound traffic).
• Audit third-party integrations – Before connecting a skill to Slack, Lark, or an external API, verify the integration's privacy policy and confirm no unnecessary data flows outside your organization.
• Use VPN or private networks for sensitive data – Route skill traffic through a corporate VPN or private network if skills access databases, internal tools, or customer information.

Monitoring

• Log all skill executions – Record who ran which skill, when, and what data it accessed; review logs weekly for unusual patterns (skills running at odd times, accessing unexpected services).
• Set alerts for permission changes – Notify your team immediately if a skill's access level is modified or a new skill is deployed; this catches unauthorized changes quickly.
• Track dependency updates – Monitor when Refly, Claude, or underlying libraries release security patches and apply them within 2 weeks of release.

Red flags to watch for

• Undocumented or unclear skills – If you cannot explain what a skill does, who built it, or what data it touches, treat it as high-risk and remove it until someone audits the code.
• Skills that handle passwords or payment data – Any skill that stores, processes, or transmits passwords, credit card numbers, or health information should be rare and reviewed by security or compliance staff before use.
• Rapid version changes or no maintenance – If Refly, a skill dependency, or a third-party integration releases multiple versions in short periods or stops releasing security updates, plan to migrate away.
• Requests to loosen controls – Be skeptical of pressure to disable MFA, share credentials, or grant "admin to everything" access; this is how breaches happen.