Individual skill
external-integrations
How Clips connects to Slack and Atlassian/Jira, and the provider-API boundary for credentialed integrations. Use when installing or debugging the Slack app, connecting Atlassian/Jira, or adding raw provider API access to a Clips integration.
templates/clips/.agents/skills/external-integrations/SKILL.md
Source commit ff01b4009091c2140edb34d6f790ec64e7823356
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 7,637
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agents Repository topic
- ai Repository topic
- react Repository topic
- agent-native Repository topic
- typescript Repository topic
- agent-framework Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- framework Repository topic
- generative-ui Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,907 bytes
Read excerpt
# External Integrations
## Slack
Slack installs should go through the Clips Settings OAuth flow (`connect-slack`,
`/api/slack/oauth/callback`) so each Slack workspace gets its own encrypted bot
token in `app_secrets`. `SLACK_BOT_TOKEN` is only a legacy single-workspace
fallback and must remain behind the team allowlist.
Link previews are handled by the unfurl webhook; see the **video-sharing** skill
for the `/api/slack/unfurl` contract, the required scopes and events, and which
clips may produce a playable video block.
## Atlassian / Jira