Cc Sdd New Agent
gotalab/cc-sdd
Add or extend coding-agent support in cc-sdd by executing the SOP in docs/cc-sdd/sop-new-agent.md end-to-end.
Linear ticket management best practices. An agent skill from bybren-llc/safe-agentic-workflow.
Install Linear Sop
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sop --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/linear-sop .claude/skills/linear-sop && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .claude/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sopType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/linear-sop .agents/skills/linear-sop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .agents/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/linear-sop .cursor/skills/linear-sop && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .cursor/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bybren-llc/safe-agentic-workflow.git --path .claude/skills/linear-sop--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/linear-sop .gemini/skills/linear-sop && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .gemini/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sopInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/linear-sop .github/skills/linear-sop && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .github/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bybren-llc/safe-agentic-workflow linear-sop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/linear-sop .opencode/skills/linear-sop && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linear-sop" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.claude/skills/linear-sop into .opencode/skills/linear-sop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-sop", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linear-sop- GitHub stars
- 423
- Token cost
- ~1.8k tokens
- SKILL.md length
- 445 words
- Files
- 2
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- MIT
At a glance
Linear ticket management best practices. An agent skill from bybren-llc/safe-agentic-workflow.
- Creating issues
- SKILL.md covers Purpose, When This Skill Applies, Linear MCP Tools and Program Structure, plus 7 more sections
- Reaches github.com
- Updating status
What it does
Linear Sop is an agent skill from bybren-llc/safe-agentic-workflow. Linear ticket management best practices. Use when creating issues, updating status, or attaching evidence. Provides evidence templates for dev/staging/done phases.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Business, Finance & HR, covering Operations and SOPs. The repository describes itself as: SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!)… The licence is MIT.
When your agent uses it
- Creating issues
- Updating status
- Attaching evidence
Example prompts
- “/linear-sop”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep
What it can do on your machine
Read from SKILL.md and the folder at commit 26ca58b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linear Sop loads about 1.8k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 445 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bybren-llc/safe-agentic-workflow at commit 26ca58b, republished under its MIT licence (© bybren-llc). 445 words, ~1,842 tokens.
Download SKILL.mdSave it as
.claude/skills/linear-sop/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- linear-sop
- description
- Linear ticket management best practices. Use when creating issues, updating status, or attaching evidence. Provides evidence templates for dev/staging/done phases.
- allowed-tools
- Read, Grep
Linear SOP Skill
Purpose
Guide consistent Linear ticket management. Provides evidence templates for the mandatory dev/staging/UAT evidence policy.
When This Skill Applies
Invoke this skill when:
- Creating new Linear issues
- Updating ticket status
- Attaching evidence to tickets
- Parsing acceptance criteria
- Working with UUIDs and issue IDs
Linear MCP Tools
Reading Issues
# Get issue by identifier
mcp__{{MCP_LINEAR_SERVER}}__get_issue({ id: "{{TICKET_PREFIX}}-459" })
# List issues with filters
mcp__{{MCP_LINEAR_SERVER}}__list_issues({
team: "{{PROJECT_TEAM_NAME}}",
state: "In Progress",
assignee: "me",
})Creating Issues
mcp__{{MCP_LINEAR_SERVER}}__create_issue({
title: "feat(scope): description",
team: "{{PROJECT_TEAM_NAME}}",
description: "## Summary\n\n...",
labels: ["feature", "sprint-1"],
parentId: "parent-uuid", // Optional - for sub-issues
})Updating Issues
mcp__{{MCP_LINEAR_SERVER}}__update_issue({
id: "{{TICKET_PREFIX}}-459",
state: "Done",
})Adding Comments
mcp__{{MCP_LINEAR_SERVER}}__create_comment({
issueId: "{{TICKET_PREFIX}}-459",
body: "**Dev Evidence**\n\n...",
})Program Structure
For work that spans many issues, Linear has objects above the issue. Use them; do not flatten a program into a flat list of tickets.
The Hierarchy
Initiative the program (one per program)
└── Project a Unit of Work — one coherent outcome
├── Milestone an AI-DLC phase: Inception, Construction, Operations
└── Issue a Story
└── Sub-issue a Mob Elaboration task (created during Inception, not before)Prerequisite: labels must already exist
Program build-out assumes these label namespaces are pre-created in the workspace. Create them before building the program, not during:
bolt:0…bolt:N— which Bolt an issue belongs toagent:*— the lead role (must match an actual agent name in.claude/agents/)
Labels are workspace-scoped in Linear — do not create team-scoped duplicates.
Streams
Linear sub-initiatives require an Enterprise plan. If your workspace has it, model program streams as sub-initiatives under the initiative. If it does not, encode the stream as project priority instead — highest-risk stream gets Urgent/High, follow-up stream gets Medium. Both are valid; pick based on your plan tier.
Dependency Wiring
Build the dependency DAG with issue relations:
mcp__{{MCP_LINEAR_SERVER}}__update_issue({
id: "{{TICKET_PREFIX}}-XXX",
blocks: ["{{TICKET_PREFIX}}-YYY"], // this issue must land first
blockedBy: ["{{TICKET_PREFIX}}-ZZZ"], // this issue waits on that one
})Use relatedTo for soft links that inform but do not block.
Wire so the enforcement lands before the thing it enforces — see the safe-ai-dlc skill for the
four dependency-wiring heuristics.
Re-parenting existing issues
When a program absorbs tickets that already exist, update them into the project — never recreate them. Duplicates break traceability and split the evidence trail.
Show full SKILL.md (191 more words)Show less
Evidence Policy (MUST)
Every issue requires evidence at each phase:
| Phase | Required? | Content |
|---|---|---|
| Dev | MUST | Implementation proof |
| Staging | MUST | UAT validation (or N/A) |
| Done | MUST | Final verification |
Evidence Templates
Dev Evidence Template
**Dev Evidence**
**PR**: https://github.com/{{ORG_NAME}}/{{REPO_NAME}}/pull/XXX
**Commit**: [short-hash]
**Branch**: {{TICKET_PREFIX}}-XXX-description
**Implementation:**
- [x] Feature implemented
- [x] Tests passing
- [x] Lint passing
**Verification:**
\`\`\`bash
yarn ci:validate
# Output: All checks passed
\`\`\`Staging/UAT Evidence Template
**Staging Evidence**
**Environment**: Pop OS dev server
**URL**: http://pop-os:3000
**Validation Steps:**
1. Deployed to staging: [timestamp]
2. Smoke test passed: [yes/no]
3. Feature verified: [description]
**UAT Status:** [Passed/Pending/N/A]
If N/A, reason: [e.g., "Dev tooling only - no user-facing changes"]Done Evidence Template
**Done Evidence**
**PR Merged**: https://github.com/{{ORG_NAME}}/{{REPO_NAME}}/pull/XXX
**Merge Commit**: [hash]
**Final Checklist:**
- [x] All acceptance criteria met
- [x] Documentation updated (if applicable)
- [x] No regressions detectedAcceptance Criteria Parsing
When reading issue descriptions, extract ACs:
## Acceptance Criteria
- [ ] User can perform action X
- [ ] System responds with Y
- [ ] Error handling for ZConvert to testable checklist:
const acceptanceCriteria = [
{ criterion: "User can perform action X", verified: false },
{ criterion: "System responds with Y", verified: false },
{ criterion: "Error handling for Z", verified: false },
];Status Workflow
Backlog -> Ready -> In Progress -> Testing -> Ready for Review -> DoneGitHub-Linear Auto-Sync
Tickets referenced in commit messages (e.g., [{{TICKET_PREFIX}}-123]) automatically move to Done when the PR merges. Child stories not referenced in any commit message must be manually closed after merge.
Best practice: Reference Feature-level tickets in commit messages. After merge, manually close orphaned child stories that weren't referenced.
Status Update Guidelines
| From | To | When |
|---|---|---|
| Backlog | Ready | Sprint planning |
| Ready | In Progress | Work starts |
| In Progress | Testing | PR created |
| Testing | Ready for Review | Tests pass, UAT complete |
| Ready for Review | Done | POPM approval or auto-sync via PR merge |
UUID Handling
Linear uses UUIDs internally. When working with APIs:
// Issue identifiers (human-readable)
const issueId = "{{TICKET_PREFIX}}-459";
// UUIDs (API operations)
const uuid = "ef6a5fa0-2b46-417f-8266-dea2d187b10a";
// Get UUID from identifier via MCP tool
// mcp__{{MCP_LINEAR_SERVER}}__get_issue({ id: "{{TICKET_PREFIX}}-459" })
// Returns issue object with .id property containing UUIDCommon Operations
Link PR to Issue
PRs are automatically linked when:
- Branch name contains
{{TICKET_PREFIX}}-XXX - PR title contains
[{{TICKET_PREFIX}}-XXX]
Create Sub-Issue
mcp__{{MCP_LINEAR_SERVER}}__create_issue({
title: "Sub-task description",
team: "{{PROJECT_TEAM_NAME}}",
parentId: "parent-issue-uuid",
})Query by Label
mcp__{{MCP_LINEAR_SERVER}}__list_issues({
label: "sprint-1",
team: "{{PROJECT_TEAM_NAME}}",
})Authoritative References
- Agent Workflow SOP:
docs/sop/AGENT_WORKFLOW_SOP.md - Linear MCP Docs: Built into Claude Code
- CONTRIBUTING.md: Workflow documentation
© bybren-llc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .claude/skills/linear-sop of bybren-llc/safe-agentic-workflow.
- SKILL.md
- README.md
Open the folder on GitHubat commit 26ca58b
Compare with similar skills
Linear Sop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linear Sop this skillbybren-llc/safe-agentic-workflow | 423 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Cc Sdd New Agentgotalab/cc-sdd | 3.7k | — | ~1.1k | Automated safety check: Pass | MIT | |
| DBS Business Toolkit Entrydontbesilent2025/dbskill | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Agent Sop Authorstrands-agents/agent-sop | 1.2k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Diffusion Narrative Denouncingcanwhite/Krebs | 1k | — | ~831 | Automated safety check: Pass | MIT | |
| Company Researchsimonlin1212/Vibe-Research | 2.6k | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
DBS Business Toolkit Entry
dontbesilent2025/dbskill
Chinese-language entry skill for the dontbesilent business toolkit: onboards new users, orchestrates tasks across sub-skills, runs numbered prompts and lists hidden ones.
Agent Sop Author
strands-agents/agent-sop
Create (or update) and validate Agent SOPs (Standard Operating Procedures) - markdown-based workflows that guide AI agents through complex, multi-step tasks with RFC 2119 constraints.
Diffusion Narrative Denouncing
canwhite/Krebs
基于"扩散模型叙事去噪流"的小说写作 SOP。将 AI 视为去杂质机器，通过锁定全局信号、预测叙事噪声、精准去噪、随机修正四个步骤，解决 AI 翻译腔、逻辑断层和故事平淡的问题。
Company Research
simonlin1212/Vibe-Research
A 股 / 港股 / 美股个股研究六阶段 SOP(profile → financials → estimates → valuation → risk → report),Phase 0 范围 = 财务估值闭环。当任务是研究 / 分析 / 评估一只或多只已指定代码的个股时使用(港股 / 美股的口径差异见 §7);规定每阶段取哪些数据、调哪些 calc 函数、必须落盘什么产物、过什么…
Polanyi Perspective
0xenzyme/polanyi-skill
Michael Polanyi 的思维框架。用 Polanyi 视角分析隐性知识、技能习得、经验传承、师徒制、 知识管理、学习方法、AI/工具替代边界、科学共同体与后批判哲学问题。
More from bybren-llc/safe-agentic-workflow
All 42 skills in this repoMulti-Agent Coordination Template
bybren-llc/safe-agentic-workflow
Agent assignment matrix, blocker escalation, and TDM coordination patterns. Use when assigning work to specialist agents, managing blockers across agents…
API Route Patterns
bybren-llc/safe-agentic-workflow
API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…
Technical Documentation Templates
bybren-llc/safe-agentic-workflow
Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…
Deployment SOP Checklist
bybren-llc/safe-agentic-workflow
Deployment workflows, pre-deploy validation, smoke testing, and rollback procedures. Use when deploying to staging or production, running smoke tests…
Frontend Patterns Template
bybren-llc/safe-agentic-workflow
Frontend patterns for modern web frameworks, component libraries, auth flows, and analytics. Use when building UI components, creating pages, implementing…
Advanced Git Operations
bybren-llc/safe-agentic-workflow
Advanced git operations including rebase, bisect, cherry-pick, and conflict resolution. Use when rebasing feature branches, debugging with bisect…
Related
Categories
Questions about Linear Sop
What does Linear Sop do?
Linear ticket management best practices. An agent skill from bybren-llc/safe-agentic-workflow. Linear Sop is an agent skill from bybren-llc/safe-agentic-workflow. Linear ticket management best practices.
When should I use Linear Sop?
Linear Sop fits situations like: creating issues; updating status; attaching evidence.
How do I install Linear Sop in Claude Code?
Run `npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a claude-code`. Or copy the skill folder (.claude/skills/linear-sop in bybren-llc/safe-agentic-workflow) into .claude/skills/linear-sop in your project. Claude Code loads it when a task matches its description.
How do I install Linear Sop in Codex?
Run `npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a codex`. Or copy the skill folder (.claude/skills/linear-sop in bybren-llc/safe-agentic-workflow) into .agents/skills/linear-sop in your project. Codex loads it when a task matches its description.
Can I use Linear Sop in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bybren-llc/safe-agentic-workflow --skill linear-sop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-sop, .gemini/skills/linear-sop, .github/skills/linear-sop and .opencode/skills/linear-sop in your project.
What does Linear Sop need to run?
SKILL.md names no scripts, command-line tools or credentials: Linear Sop is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep.
Does Linear Sop access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Linear Sop safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linear Sop use?
Linear Sop is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linear Sop use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Linear Sop?
Skills that share tags, products or a category with Linear Sop: Cc Sdd New Agent (gotalab/cc-sdd, 3.7k stars), DBS Business Toolkit Entry (dontbesilent2025/dbskill, 11k stars), Agent Sop Author (strands-agents/agent-sop, 1.2k stars) and Diffusion Narrative Denouncing (canwhite/Krebs, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linear Sop?
bybren-llc (a GitHub organization) maintains it in bybren-llc/safe-agentic-workflow, which has 423 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on July 20, 2026.
Source: bybren-llc/safe-agentic-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.