agentleFS
Sign inStart free
OpenCovenOpenCoven/coven/skills/project-manager/SKILL.md

project-manager

Skill75 starsChanged 4 months agoMITView on GitHub

Manage project-scoped knowledge bases with notes, decisions, and bookmarks. Use when the user wants to create/manage projects, add/view/search notes or decisions for a project, manage bookmarks (add, list, tag to projects), switch project context for conversation, or search across projects. Triggers on phrases like "project", "bookmark", "add a note to", "let's talk about [project]", "switch to [project]", "list projects", "search projects".

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use boat-machines, controllers-policy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Th0rgalSkill

    boat-machines

    When and how a mission should rent boat.dev managed VMs: whether to use one at all, size choice, one warm snapshot per project, forking the parent VM, sharing a VM between sequential siblings, stopping instead of idling, budgets and cleanup. Use before spawn_managed_machine, start_mission(remote_node_id=\"auto-managed:...\"), fork, snapshot or stop/resume tools.

    Also in 3 projects that use this

  • Th0rgalSkill

    controllers-policy

    Autonomy contract and routing index for autonomous project controllers. Loaded every tick; carries the rules that must survive cron-prompt rewrites.

    Also in 3 projects that use this

  • FlatbreadLabsSkill

    orchestrator-executor

    Coordinate large, long-running, parallel, architecture-sequenced, or isolated-worktree tasks with a cost-conscious orchestrator/executor model. Use when work needs a dependency graph, multiple agents, staged integration, durable asynchronous coordination, or independently reviewable changes.

    Also in 3 projects that use this

  • SashankMeka1Skill

    orchestrator-worker

    Use this skill when designing or building a multi-agent automation harness (e.g. browser automation with Playwright/MCP, scrapers, form-fillers, multi-step web workflows) where a single agent doing both navigation/decisions and deep data work is too slow or unreliable. Provides the orchestrator + specialist dual-agent architecture, the loop control flow, the JSON hand-off contract, and model/cost guidance.

    Also in 3 projects that use this

  • ClineSkill

    data-analyst

    Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).

    Also in 3 projects that use this

  • JeffallanSkill

    devops-engineer

    Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.

    Also in 3 projects that use this

  • +4 more from Th0rgal

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use short incremental IDs: b1, b2, b3...

    line 39
  2. Distinctive:

    When adding, auto-fetch the page title if not provided

    line 40
  3. Very specific:

    Create projects/<slug>/CONTEXT.md with project name, description, and any initial info

    line 46
  4. Very specific:

    Use ## HH:MM headers for multiple entries per day

    line 51
  5. Distinctive:

    If the note contains a decision, prefix with Decision:

    line 52
  6. Very specific:

    Add project slug to its projects array

    line 62
  7. Very specific:

    Read recent notes: projects/<slug>/notes/ (last 3 files)

    line 66
  8. Very specific:

    Read bookmarks tagged to this project from _bookmarks.json

    line 67
  9. Distinctive:

    Use this context to inform conversation

    line 68
  10. Very specific:

    Use grep -ri across projects/ for text search

    line 75
  11. Distinctive:

    When chatting about a project, always load:

    line 85
  12. Distinctive:

    Keep context loading efficient.

    line 90

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Manager

Manage project-scoped context in projects/ within the workspace.

File Structure

projects/
├── _bookmarks.json         ← global bookmarks store
├── <project-slug>/
│   ├── CONTEXT.md          ← project overview, status, key info
│   └── notes/
│       └── YYYY-MM-DD.md   ← dated notes (append-style)

Bookmarks

Stored in projects/_bookmarks.json as an array:

[
  {
    "id": "b1",
    "url": "https://example.com",
    "title": "Example Site",
    "description": "Optional description",
    "projects": ["project-slug"],
    "added": "2026-02-08"
  }
]
  • Bookmarks exist independently and can be tied to zero or more projects
  • Use short incremental IDs: b1, b2, b3...
  • When adding, auto-fetch the page title if not provided

Actions

Create project

  1. Slugify the name (lowercase, hyphens)
  2. Create projects/<slug>/CONTEXT.md with project name, description, and any initial info
  3. Create projects/<slug>/notes/ directory

Add note to project

  1. Append to projects/<slug>/notes/YYYY-MM-DD.md (today's date)
  2. Use ## HH:MM headers for multiple entries per day
  3. If the note contains a decision, prefix with Decision:

Add bookmark

  1. Read projects/_bookmarks.json
  2. Generate next ID (b1, b2, ...)
  3. Append new bookmark with optional project tags
  4. Write back

Link bookmark to project

  1. Find bookmark by URL or ID
  2. Add project slug to its projects array

Switch context / Chat about project

  1. Read projects/<slug>/CONTEXT.md
  2. Read recent notes: projects/<slug>/notes/ (last 3 files)
  3. Read bookmarks tagged to this project from _bookmarks.json
  4. Use this context to inform conversation

List projects

  1. List directories in projects/ (excluding files starting with _)
  2. Show name + first line of CONTEXT.md for each

Search across projects

  1. Use grep -ri across projects/ for text search
  2. Report which project(s) and file(s) matched

List bookmarks

  1. Read _bookmarks.json
  2. Optionally filter by project tag
  3. Display as a clean list with titles and URLs

Context Loading

When chatting about a project, always load:

  1. CONTEXT.md — the full project overview
  2. Latest 3 note files — recent activity
  3. Tagged bookmarks — relevant links

Keep context loading efficient. Only read what's needed for the conversation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free