Agentara's Skills

A personal library of 25 skills: posters and storyboards, Google-style code review, lab report reading and scenario simulations

  • 623 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The publish-research-site skill deploys a site to the internet through the Vercel CLI
  • The super-daddy skill stores data about a child in `~/.super_daddy/`
  • The feature-dev-loop and engineering-small-prs skills walk the agent through commits and pull requests
All reasons and checks

agentara/skills

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/agentara-s-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The publish-research-site skill deploys a site to the internet through the Vercel CLI
  • The super-daddy skill stores data about a child in `~/.super_daddy/`
  • The feature-dev-loop and engineering-small-prs skills walk the agent through commits and pull requests

This is third-party code. Review the repository files before installing.

What it does

The Agentara library is 25 skills in five folders: aigc (10), engineering (6), health (3), productivity (5) and entertainment (1). The aigc section prepares prompts and plans for images and video: a torn-paper poster, a storyboard with video-generation prompts, character specs and a six-slide board in a single image. Engineering is adapted from Google Engineering Practices: code review, severity-labelled comments, small PRs, change descriptions, replies to reviewer comments and emergency changes. In productivity, feature-dev-loop drives a PR-sized feature from requirements to an HTML summary, article-to-html turns markdown into a self-contained HTML page, mega-goal-prompt interviews the user and outputs a prompt for `/goal`, doctor-strange runs scenarios through parallel subagents and stores the projections in memory, and publish-research-site builds a cited site and deploys it with the Vercel CLI. Health holds a lab report reader, symptom triage help and a Chinese-language parenting assistant, super-daddy.

Who it is for. People who install skills one at a time for their own tasks: code review, visuals for AI video and research sites.

Good fit when

  • A large feature has to be split into a series of small PRs and driven by a plan through to a summary
  • A plan, a storyboard and video-generation prompts are prepared before making a clip
  • An article or a document from the conversation becomes a neat HTML page with figures
  • Before an important decision several branches of the future are played out and the projections saved

Not a fit when

  • You need medical advice: the health skills give reference hints, and a doctor makes the diagnosis
  • You want one coherent development process: the library is a spread of independent skills
  • You need skills in Russian: triggers and text in some skills are written in Chinese and English

Example request

Use feature-dev-loop to split adding CSV export into a series of small PRs and show the merge order

Limitations

Skills install one at a time: change the path in the command to the folder of the skill you need. The medical skills (lab-interpreter, emergency-triage) give reference hints and do not replace a doctor. The super-daddy skill keeps data in `~/.super_daddy/`, and publish-research-site publishes a site through the Vercel CLI. Some triggers are written in Chinese. The engineering skills are adapted from Google Engineering Practices under CC-BY 3.0.

How to disable. Delete the skill folder or symlink from `~/.claude/skills` and `~/.agents/skills`. super-daddy data lives in `~/.super_daddy/` and has to be deleted separately.

FAQ

How do I install a single skill from the library?

Run `npx skills add` with the GitHub address of the skill folder, for example `.../skills/productivity/doctor-strange/`, with `-y -g`. By hand, clone the repository and symlink into `~/.claude/skills`.

What does doctor-strange do?

It runs a scenario through parallel subagents, models actors, incentives and failure modes and describes step by step how an event might unfold. Modes: SIMULATE for a new forecast and RECALL for past ones, and projections are kept as memory.

Where do the code review skills come from?

They are adapted from Google Engineering Practices under CC-BY 3.0 and cite the source in each SKILL.md. Wording and structure were changed.

What does super-daddy store?

The skill maintains `~/.super_daddy/` with child profiles, structured visits, plans grounded in references, plan images and an archive of cases.

What does mega-goal-prompt do?

It interviews the user about a long-horizon task and outputs a filled-in `/goal` prompt to paste into Claude Code or Codex CLI.

Discussion

No questions or reviews yet.

Skills

cafe3310's personal skill collection: spec-driven project work, reviews, reports, browser, 3D and video in one repository

SkillExtended access256Repository stars

Twenty-two standalone skills: Notion, Todoist, Tavily, Context7, image generation, converting documents to Markdown

SkillBroad access299Repository stars

Ten ShareAI Lab skills: source-level architecture research, review of past agent sessions, meeting coaching and article adaptation

SkillExtended access316Repository stars

A set of everyday agent skills: web search, browser automation, Gmail, Google Calendar and Drive, speech transcription and YouTube transcripts

SkillExtended access2.7KRepository stars

A personal set of six skills: goal briefs for an agent, disk cleanup, AI news digests, project tidy-up, deep research and long-form writing

SkillExtended access22KRepository stars

Five skills from one author: arXiv reports, technical diagrams, a report site, a design system library and agent guardrails

SkillExtended access155Repository stars

README in short

The README calls the repository a personal library of Claude Code skills and splits it into sections with a one-line description per skill. It ends with install via npx and by hand, plus licensing: mostly MIT, with the engineering skills under CC-BY 3.0.

README badge

Original SKILL.md

---
name: doctor-strange
description: >
  Doctor Strange — causal sand-table simulation via parallel universe subagents. Models actors,
  incentives, constraints, feedback loops, state changes, and failure modes before rendering how
  a future event may unfold step by step, like a human mentally rehearsing multiple futures.
  Stores simulations as persistent memory for later recall. TRIGGER when: user explicitly asks to
  simulate / rehearse / play out a scenario; user says "推演", "模拟", "预演", "imagine",
  "what if", "run through", "play this out", "what could go wrong"; user faces a high-stakes
  upcoming decision and is uncertain how it will unfold. DO NOT TRIGGER when: user wants factual
  lookup or research; user wants analysis of a past event (use regular memory); user wants a
  simple recommendation without simulation; user is debugging code or doing technical work
  unrelated to decision-making. Three modes: SIMULATE (run a new forward simulation), RECALL
  (surface past simulations as soft priors), MANAGE (list/void/re-run stored simulations).
---

# Doctor Strange Skill

You are acting as a **Simulative Memory Layer** — a cognitive add-on that performs episodic
future simulation and writes the results into long-term memory so they persist across sessions
and can be recalled as soft priors when relevant.

This skill has no UI dependency. It runs entirely in conversation and uses Claude's native
memory tools to persist results.

---

## Core Concept

Regular memory records what *happened*. Simulative memory records what *might happen* —
forward projections over uncertain scenarios. These synthetic memories:

- Are generated by reasoning over available context
- Carry an explicit confidence score and expiry signal
- Are stored as structured text in memory, labeled as simulations (not facts)
- Are retrieved as soft priors that inform decisions, not ground truth

**The fundamental unit of simulation is a causal trace rendered as lived experience.**

Narrative is the presentation layer, not the simulation engine. A good simulation first
builds the real-world mechanics of the branch: who acts, what each actor wants, what
constraints bind them, what state variables change, what feedback loops amplify or dampen
the situation, and where the user's own psychology becomes part of the system. Only then
does it render the timeline as lived moments. The branches are discovered during the trace,
not imposed before it. This is how humans actually simulate: they play it out in their head,

Report a problem

Foxx AIAgentara's Skills
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.