---
title: "organise"
description: "README contains an index organising my repositories that are related to Claude Code."
type: skill
canonical_url: https://claudary.paisolsolutions.com/skills/organise
source: "Claudary"
difficulty: intermediate
author: "Claude Code Knowledge Pack"
date: 2026-07-10T11:31:35.384Z
license: CC-BY-4.0
attribution: "organise — Claudary (https://claudary.paisolsolutions.com/skills/organise)"
---

# organise
README contains an index organising my repositories that are related to Claude Code.

## Overview

README contains an index organising my repositories that are related to Claude Code.

Please parse the current list.

If you can identify ways in which the readme could be better organised, implement those changes. 

The organisational approach:

- Repositories reflecting a common theme are grouped
- A short description is provided explaining the cluster (immediately beneath the header). For example: "These repositories explore how Claude can work with MCPs."
- Then the repos are listed as H3, link badge, one line description, horizontal line

My overall approach to organising readmes, which you should adhere to: 

- Create enough sections that are useful for organising the repos into common clusters/groups 
- Create no more than that level of organisation! 
- Duplication is not ideal but is permitted if we have two very specific categories and a repo(s) belongs in both categories, for example

---

Source: [Claudary](https://claudary.paisolsolutions.com/skills/organise) · https://claudary.paisolsolutions.com