Standards for OCaml project metadata files. Use when initializing a new OCaml library/module, preparing for opam release, setting up CI, or discussing project structure. Not for normal code edits.
/plugin marketplace add avsm/ocaml-claude-marketplace/plugin install avsm-ocaml-dev-plugins-ocaml-dev@avsm/ocaml-claude-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
templates/LICENSE-ISC.mdtemplates/LICENSE-MIT.mdtemplates/README.template.mdtemplates/ci-github.ymltemplates/ci-gitlab.ymltemplates/ci-tangled.ymltemplates/dune-project.templatetemplates/dune-root.templatetemplates/gitignoretemplates/ocamlformatInvoke this skill when:
Do not use for:
Read configuration from ~/.claude/ocaml-config.json:
{
"author": {
"name": "Author Name",
"email": "author@example.com"
},
"license": "ISC",
"copyright_year_start": 2025,
"ci_platform": "github",
"git_hosting": {
"type": "github",
"org": "username"
},
"opam_overlay": {
"enabled": false,
"path": null,
"name": null
},
"ocaml_version": "5.2.0"
}
If config file doesn't exist, prompt user for values and offer to save.
Every OCaml source file should start with a license header. Use the configured license.
ISC License:
(*---------------------------------------------------------------------------
Copyright (c) {{YEAR}} {{AUTHOR_NAME}} <{{AUTHOR_EMAIL}}>. All rights reserved.
SPDX-License-Identifier: ISC
---------------------------------------------------------------------------*)
MIT License:
(*---------------------------------------------------------------------------
Copyright (c) {{YEAR}} {{AUTHOR_NAME}} <{{AUTHOR_EMAIL}}>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND.
SPDX-License-Identifier: MIT
---------------------------------------------------------------------------*)
Use Dune for builds with automatic opam file generation.
See templates/dune-project.template for the full template.
Key points:
(generate_opam_files true)(maintenance_intent "(latest)") for actively maintained projects(version ...) field - added at release timeSee templates/dune-root.template.
Include (data_only_dirs third_party) to ignore fetched dependency sources.
See templates/gitignore for the standard template.
Always include:
_build/third_party/*.installUse OCamlFormat with default styling.
See templates/ocamlformat - current version 0.28.1.
Templates available for:
templates/ci-github.ymltemplates/ci-tangled.ymltemplates/ci-gitlab.ymlSelect based on user's ci_platform configuration.
See templates/README.template.md for structure.
Include:
Essential files:
README.mddune-projectdune (root).ocamlformat.gitignoreLICENSE.mdTest files:
test/dunetest/test_*.mlWhen using templates, replace:
{{PROJECT_NAME}} - snake_case project name{{PROJECT_NAME_KEBAB}} - kebab-case project name{{AUTHOR_NAME}} - from config{{AUTHOR_EMAIL}} - from config{{YEAR}} - current year{{LICENSE}} - license identifier (ISC, MIT, etc.){{OCAML_VERSION}} - minimum OCaml version{{GIT_URL}} - full git URL{{GIT_HOSTING_TYPE}} - github, tangled, or gitlabThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.