SecondShiftgives the boring checks a shift.

Write skills with your coding agent. Commit them to Git. Run them with approved access, execution limits, and shared results.

Try it locally →Deploy for your team →
Works with
ModelsOpenAIAnthropicOpenRouterFireworksTogether AIBasetenToolsGitHubSentryGrafanaDatadogPagerDutyWildEdgeDeliverySlackDiscordTeams

Turn your skills into your team’s heartbeat.

Run the checks, reviews, and tasks that keep your team running.

  1. 01Developers

    Write a skill.

    Use Codex, Claude Code, or OpenCode. Connect to SecondShift over MCP to discover allowed tools and validate your configuration. Review and merge in Git.

    Connect your coding agent →
  2. 02Owners & admins

    Approve its access.

    Owners connect models and services and approve job access. Admins set limits and enable schedules. Skills cannot expand their own permissions.

    Roles and permissions →Security model →
  3. 03SecondShift

    Run skills when you need them.

    Start a run yourself, set a schedule, or trigger it from another service. Your team can review the results, tool activity, and cost of every run.

    How execution works →

For yourself: run locally and manage your own skills. Try it locally →

For your team: share a server, approvals, and run history. Deploy →

Simplest example

How jobs work →
.agents/skills/docs-drift/SKILL.md
---
name: docs-drift
description: Find stale documentation.
---

# Documentation drift

Check docs against the repository.
Report broken links, paths, and commands.
Do not modify files.
.secondshift.yaml
version: 1

jobs:
  docs-drift:
    name: Documentation drift
    skill: .agents/skills/docs-drift/SKILL.md
    schedule: "0 8 * * 1"
    timezone: UTC