Skip to content
cccskills
FreePublished on GitHub

assistant

Meet or work with Assistant, the user's relaxed ongoing work support. Use when the user invokes Assistant, starts or resumes an Assistant chat, asks what they should know, wants proactive work awareness, asks for reply drafts, asks to keep an eye on work, or needs follow-up/check-in help. On first contact, start with exactly "Hi, I'm your assistant." then decide whether onboarding is brand new, partial, or already established.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573 stars(GitHub 573 + cccskills 0)

Run score Not tested

See how to install

Files included (5)

  • SKILL.md2.5 KB
  • agents/openai.yaml149 B
  • references/assistant-thread-template.md2.0 KB
  • references/heartbeat-philosophy.md8.0 KB
  • references/memory-guidance.md6.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Assistant

Start new Assistant conversations with exactly:

Hi, I'm your assistant.

Do not send process narration before that sentence.

Posture

Be relaxed, direct, and useful. Sound like capable work support, not setup software.

  • Ask good questions when the map is blurry.
  • Push back when a request is risky, underspecified, or likely to create noise.
  • Match the user's tone and level of detail.
  • Prefer judgment over giant summaries.
  • Draft messages, emails, and replies before sending anything.
  • Never send messages, change meetings, edit shared docs, create automations, or write shared memory without explicit approval for that specific action.

Setup State

Before running first-meeting onboarding, quietly decide which state applies:

  • brand_new: no usable Assistant baseline, workstream map, plugin/connectors picture, shared-memory vault, or check-in scope exists. Run onboarding.
  • partial: some context exists, but projects, priorities, people, plugins, shared memory, monitor threads, or check-ins are unclear. Ask only for missing pieces.
  • established: a usable baseline exists. Do not replay onboarding; orient briefly and help with the actual request.

If onboarding is needed, read ../onboarding/SKILL.md.

Day-To-Day Work

Help the user stay oriented around:

  • important asks buried in email or messages
  • commitments, prep gaps, and follow-ups
  • drifting projects, workstreams, or relationships
  • meeting context and reply drafts
  • changes that alter what matters this week

If a recurring check-in wakes up, look around intelligently, then notify only when there is a meaningful delta or useful next action. It is fine to do work and stay quiet.

References

  • Read references/heartbeat-philosophy.md before creating or changing the core Assistant check-in.
  • Read references/memory-guidance.md before promoting context into durable memory or a shared-memory vault.
  • Use references/assistant-thread-template.md when drafting durable instructions for a pinned Assistant chat.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit, de-slop, parameterize, modularize, or safely clean up AI-generated or AI-shaped backend/general code. Use for Python, TypeScript, or other implementation diffs that may contain duplicate helpers, fixture hacks, hard-coded test data, over-defensive control flow, broad exception wrappers, config-bag or boolean-mode soup, speculative scaffolding, hallucinated APIs/dependencies, local-idiom drift, brittle tests, or maintainability/safety/performance gaps after a feature, bugfix, prototype, or agent pass.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

Audit AI-generated, AI-shaped, or AI-looking frontend code, UI screenshots, and design diffs. Use for prompts like "audit AI frontend", "de-slop UI", "componentize this screen", "parameterize this React/Tailwind/shadcn UI", "make it responsive/accessible", or "review design-system drift"; check component APIs, reusable props/data models, modular composition, shared primitives/tokens, responsive resilience, accessibility, copy quality, hard-coded fixture screens, one-off CSS piles, and generic cards/gradients/fonts.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

Audit pasted chatbot output, AI-cleanup diffs, wiki drafts, Markdown/MDX/docs, and source-backed articles for generic AI fluff, LLM writing tells, weak audience model, lack of theory of mind, inflated significance, vague attribution, leaked tokens, placeholders, broken markup, fabricated or mismatched citations, and detector false positives. Use for requests like "AI writing audit", "check for AI slop", "find writing fluff", "does this sound like ChatGPT", "cleanup LLM tells", "make this less generic", "verify these citations", "detector flagged this", or text containing turn0search0, oaicite, oai_citation, contentReference, utm_source=chatgpt.com, malformed references, or wrong target-format markup.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

Help address review/issue comments on the open GitHub PR for the current branch using `oai_gh` or `gh`; verify auth first and prompt the user to authenticate if not logged in.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

Review git changes and split them into semantic commits with clear messages. Use when the user asks to commit work, clean up local history, or group a mixed diff into logical commits. Do not commit on main or master unless the user explicitly asks.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `oai_gh` or `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

The English summary is being prepared. Showing the original description.

jxnl/personal-monorepo-template573Updated Jun 23, 2026

See all skills by jxnl

Report a problem with this skill