All this assumes the wercker scripts execute in a directory that contains a divshot.json file and the static files for your app. Would be necessary to copy the token from ~/.divshot/config/user.json

divshot.io-wercker-build.yml

box: wercker/nodejs
# Build definition
build:
  # The steps that will be executed on build
  steps:
    # A step that executes `npm install` command
    - npm-install
    # A step that executes `npm test` command
    - npm-test

    # A custom script step, name value is used in the UI
    # and the code value contains the command that get executed
    - script:
        name: deploy to divshot.io staging
        code: |
          npm install -g divshot-cli && divshot push staging --token <token from ~/.divshot/config/user.json>

Looks good, I think it is good to move this into a deploy. That way you can more easily rollback deploys and deploy builds to different targets.

# Add this to your wercker.yml below your builds and build steps
deploy:

  # The steps that will be executed on build
  steps:
    - script:
        name: deploy to divshot.io staging
        code: |
          npm install -g divshot-cli 
          divshot push $WERCKER_DEPLOYTARGET_NAME --token $DIVSHOT_TOKEN

In this example the deploy target name is used as the target name for divshot. It also assumes you have created an environment variable named DIVSHOT_TOKEN with your api token.

Hey guys, thanks :D I've taken this and added it as a guide in our documentation.

http://docs.divshot.io/integrations/wercker