anchor.diff:  
   Opskeleton generates the complete folder structure for projects:
   
  -image:https://raw.githubusercontent.com/opskeleton/opskeleton/master/img/puppet-layout.png[width=40%,hight=50%]
  -
  -==== module lifecycle
  +image:https://raw.githubusercontent.com/opskeleton/opskeleton/master/img/puppet-layout.png[width=30%,hight=50%]
  +
  +==== lifecycle
   
   Opskelaton defines a module life cycle:
   
  
positive.code: 
  An external node classifier based runner is also available under scripts/run.sh, this runner expects to get a <hostname>.yaml input file with the required node classes.
  
  
  === Deployment
  
   See [deploy](deploy.md)
  
  === Updating
  Keeping you box up to date with latest opsk version is easy, just re-generate it again and resolve conflicts by answering y/n:
  ```bash
  
negative.code: Opskelaton supports two levels of testing:
  
  * Static module testing that includes rspec and linting.
  * Integration testing using http://serverspec.org/[serverspec]and Vagrant.
  
  ```bash
  # linting all static modules
  