home.social

#claudeskills — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #claudeskills, aggregated by home.social.

fetched live
  1. Could your next Claude Code skill be a diagram? Not a diagram just describing the skill — a diagram that is the skill, executed like code. The answer is YES.

    Once you've tried it, you may not want to go back.

    antonymarcano.substack.com/p/c

    #claudecode #ai #aiaugmented #claudeskills

  2. Could your next Claude Code skill be a diagram? Not a diagram just describing the skill — a diagram that is the skill, executed like code. The answer is YES.

    Once you've tried it, you may not want to go back.

    antonymarcano.substack.com/p/c

    #claudecode #ai #aiaugmented #claudeskills

  3. Could your next Claude Code skill be a diagram? Not a diagram just describing the skill — a diagram that is the skill, executed like code. The answer is YES.

    Once you've tried it, you may not want to go back.

    antonymarcano.substack.com/p/c

    #claudecode #ai #aiaugmented #claudeskills

  4. Could your next Claude Code skill be a diagram? Not a diagram just describing the skill — a diagram that is the skill, executed like code. The answer is YES.

    Once you've tried it, you may not want to go back.

    antonymarcano.substack.com/p/c

    #claudecode #ai #aiaugmented #claudeskills

  5. Could your next Claude Code skill be a diagram? Not a diagram just describing the skill — a diagram that is the skill, executed like code. The answer is YES.

    Once you've tried it, you may not want to go back.

    antonymarcano.substack.com/p/c

    #claudecode #ai #aiaugmented #claudeskills

  6. "Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.

    Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).

    Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.

    Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."

    passo.uno/skills-are-docs/

    #TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown

  7. "Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.

    Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).

    Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.

    Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."

    passo.uno/skills-are-docs/

    #TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown

  8. "Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.

    Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).

    Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.

    Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."

    passo.uno/skills-are-docs/

    #TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown

  9. "Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.

    Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).

    Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.

    Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."

    passo.uno/skills-are-docs/

    #TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown

  10. "Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.

    Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).

    Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.

    Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."

    passo.uno/skills-are-docs/

    #TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown

  11. Coursera mua lại Udemy với $2.5B, tích hợp AI nâng cao giáo dục. Dùng #ClaudeSkills tạo sản phẩm tri thức hiệu quả: định hình kiến thức, huấn luyện AI theo SOP, xây kỹ năng thực hành, kiểm soát chất lượng. Đảm bảo học viên đạt kết quả rõ ràng, giảm hoàn tiền. Biến sản phẩm từ "học lý thuyết" thành "tri thức + thực hành" ⇒ tăng doanh thu & trung thành khách hàng. #GiáoDụcAI #SảnPhẩmTriThức #ClaudeAI #TechTrends #KhởiNghiệp

    reddit.com/r/SaaS/comments/1pp

  12. Created my first Claude Agent Skill, a skill for creating Mochi cards. Mochi is a spaced repetition app that has an API. Created my own little plugin marketplace for it in a GitHub repo github.com/JoshuaOliphant/clau

    #claudeskills #AgentSkill #MochiCards #SpacedRepetition

  13. Created my first Claude Agent Skill, a skill for creating Mochi cards. Mochi is a spaced repetition app that has an API. Created my own little plugin marketplace for it in a GitHub repo github.com/JoshuaOliphant/clau

    #claudeskills #AgentSkill #MochiCards #SpacedRepetition

  14. Created my first Claude Agent Skill, a skill for creating Mochi cards. Mochi is a spaced repetition app that has an API. Created my own little plugin marketplace for it in a GitHub repo github.com/JoshuaOliphant/clau

    #claudeskills #AgentSkill #MochiCards #SpacedRepetition

  15. Created my first Claude Agent Skill, a skill for creating Mochi cards. Mochi is a spaced repetition app that has an API. Created my own little plugin marketplace for it in a GitHub repo github.com/JoshuaOliphant/clau