写作与沟通
2,906 个结果
- After Effectsiart-aiThis skill should be used when the user asks anything about Adobe After Effects — to "write an After Effects expression", "make a wiggle / loopOut / inertial bounce", "rig a control with a slider / null", "build a MOGRT / Essential Graphics template", "export AE to Lottie or Media Encoder"; OR to "export from After Effects", "export with transparency / an alpha channel", "fix a black background…
- Shot Compositioniart-aiThis skill should be used when the user asks to "compose a frame", "set up a grid", "plan shot composition", "place the focal point", "decide where elements enter and exit", "add a parallax/camera move", "adapt a layout for 16:9 / 9:16 / 1:1", or "keep content inside safe areas". Covers grids, safe areas, focal hierarchy, and 2D/3D camera framing.
- Venice ErrorsVenice.aiHandle Venice API errors correctly. Covers the error body shapes (StandardError, DetailedError with validation details/issues, OpenAI-style context_length_exceeded, upstream provider rejections with request_id including TypeSafe/FastAPI validation errors, ContentViolationError, ProviderContentPolicyError, PayloadTooLargeError, the two x402 402 bodies), every meaningful status code (400-504…
- Pr CreatorMatthew BlodeCreates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "open a PR", "rewrite the PR description", or "polish this PR".
- Llm WikinashsuQuery the user's LLM Wiki knowledge base (the LLM Wiki desktop app at 127.0.0.1:19828 — NOT Obsidian, Notion, Apple Notes, Logseq, or any other PKM tool). Trigger ONLY when the user explicitly names LLM Wiki, says 'my wiki', 'my 知识库 / 知识库 / knowledge base', or asks things like 'what does my wiki say about X', 'read wiki page Y', 'show my wiki graph / 知识图谱', 'search in my LLM Wiki project'…
- manavmishra/ZeroSlopManav技能合集Open-source Agent Skill that finds and removes AI slop from your writing
- Working With Claude CodeobraUse when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
- Zero SlopManavEdit drafts into natural prose, inspect AI-sounding patterns, or review how a specified audience might respond passage by passage. Zero Slop runs inside the user's existing AI assistant with local tools that protect source details. Use for humanizing or de-slopping writing, polishing outward-facing prose, social drafts, final editorial checks, or an explicit simulated reader review.
- Pydantic Ai HarnessPydanticExtend Pydantic AI agents with capabilities from pydantic-ai-harness -- the Coder coding agent, file and shell tools in local or sandboxed workspaces (Modal, E2B, Sprites, smolvm), Code Mode, sub-agents and planning, memory and skills, context compaction, guardrails and spend limits, web research and browsers, hosted SaaS integrations, step persistence, and background agents on Render Workflows.
- LintlangHermes LabsLint AI agent instruction files (SKILL.md, CLAUDE.md, AGENTS.md, GEMINI.md), tool definitions, system prompts, and agent configs with the deterministic LintLang CLI. Use when writing, editing, or reviewing agent instructions to catch ambiguous tool descriptions, missing stop conditions, schema/description mismatches, mixed output formats, or prompts embedded in Python before they reach runtime.
- Missing TriggerHermes LabsWrites a status summary from a template.
- Campaigns InterviewClayUse when a fresh Clay Sequencer campaign has no meaningful subject or body copy and needs its first draft.
- Campaigns Sequence ReviewingClayReview Clay Sequencer copy as the intended recipient and identify only material, actionable objections.
- Campaigns Sequence WritingClayDraft and revise complete Clay Sequencer email sequences using supplied campaign strategy and context.
- ClayClayClay — start here. A table of contents for working with Clay and which skill to use for each thing — audiences (the workspace's own people/companies/deals), campaigns (create, improve, and analyze outbound email sequences), ad syncs (push audience segments to ad platforms), search (find net-new people/companies), routines (run Clay-managed and custom functions), tables (query/export data), the…
- Content StrategyInfrasity-LabsDefine what content a product needs, how it should be structured, and who owns it.
- Cover LetterInfrasity-LabsWrite a tailored cover letter for a specific job posting
- Critique Information DensityInfrasity-LabsCritique a screen's information density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure.
- Dotnet Run FileNikiforovAllRun script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
- SignalsClayClay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience. Use for any request about a workspace's signals: which ones exist, what one watches or writes to, whether one is running, turning one on or off, and why one is or is not producing events.
- Workflows Campaign EnrollmentClayEnrol Audiences people into a Clay campaign from a workflow step, using the "Enroll in campaign" action (`enroll-lead-in-sequence`). Use when a workflow should start emailing the people it just processed.
- Workflows Discover ActionsClayClay workflows — discover available actions for workflow nodes (email lookup, company enrichment, phone finders, etc.) and inspect their input and output schemas. Use while building a workflow.
- Prd TemplatesslgoodrichMaster PRD templates including problem statements, success metrics, requirements, user stories, and technical considerations. Use when writing PRDs, documenting features, defining requirements, communicating product decisions, or creating feature specifications. Covers PRD structure, writing best practices, and templates from Amazon, Google, and high-performing PM teams.
- Specification TechniquesslgoodrichMaster techniques for writing clear, complete product specifications and requirements documents (PRDs). Use when defining feature requirements, writing user stories, creating acceptance criteria, documenting API specifications, aligning cross-functional teams, reducing ambiguity, covering edge cases, or translating product vision into actionable development tasks.