agentsclimarketplace

Chrisai chatting

Skill cblanquera/chrisai/skills/chrisai-chatting

Me + LLM = Godly

Install
npx -y skills add cblanquera/chrisai --skill chrisai-chatting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use for experimental chat-session experience work, including session caching and recall, turning agent intake prompts into HTML form artifacts, and converting agent responses into readable HTML preview links.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, as published. Nobody here has run it

ChrisAI Chatting

Use this skill for experimental workflows that improve the shape, continuity, or artifact interface of chat sessions.

Do not use this skill for general conversation quality, prompt editing, broad assistant behavior design, or production application implementation unless the request is specifically about chat-session experience patterns.

Internal Workflows

Use the narrowest workflow that owns the user's requested chat-session experience artifact.

  • workflows/chat-session-caching-and-recall.md: For preserving useful chat context, producing compact recall artifacts, deciding what should be cached, and rehydrating prior session state without overloading a new conversation.
  • workflows/html-form-intake.md: For turning agent intake prompts into local HTML form artifacts that produce raw-text responses for the user to paste back into chat.
  • workflows/agent-response-to-html.md: For mirroring agent responses into a readable HTML preview link while preserving the chat response as the canonical answer, or for saving/opening HTML when the user explicitly asks.

General Rules

  • Prefer artifact-oriented outputs when the user provides or asks for HTML.
  • Preserve source meaning when transforming chat content into cache summaries, intake briefs, or HTML artifacts.
  • Separate session-memory guidance from repository memory, application state, or long-term user profile storage unless the user explicitly asks to connect those systems.
  • Do not invent persistence, storage, browser automation, or deployment behavior. Describe assumptions and ask for the missing target environment when those choices matter.

Decision Rules

  • If the task is about compacting, saving, recalling, or transferring useful chat-session context, use the chat-session caching and recall workflow.
  • If the task starts from an agent intake prompt that should be answered as a form, an HTML form submission, exported form artifact, or submitted HTML payload, use the HTML form intake workflow.
  • If the task asks for a response, summary, report, or handoff to become pretty, readable, previewed, or HTML-formatted, use the agent response to HTML workflow.
  • If the request spans multiple workflows, choose the workflow that owns the first concrete artifact and keep any follow-up workflow explicit.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.