Add terminology section to DeepWork skill documentation#216
Merged
Conversation
Jobs are collections of related workflows, and users may refer to them interchangeably. Added a Terminology section to the deepwork skill (both templates and generated files) so the agent understands this relationship and can use context to resolve ambiguity. https://claude.ai/code/session_01PryjYaPSdnV5vyFqaHi2ze
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added a "Terminology" section to the DeepWork skill documentation to clarify the distinction between "jobs" and "workflows" and help users understand how these terms relate to each other.
Changes
get_workflowsto determine the best matchFiles Modified
.claude/skills/deepwork/SKILL.md.gemini/skills/deepwork/index.tomlsrc/deepwork/templates/claude/skill-deepwork.md.jinjasrc/deepwork/templates/gemini/skill-deepwork.md.jinjaThe terminology section is consistently placed after the introductory description and before the "IMPORTANT" note about using MCP tools across all documentation variants.
https://claude.ai/code/session_01PryjYaPSdnV5vyFqaHi2ze