Alexhans commented on issue #320:
URL: 
https://github.com/apache/airflow-steward/issues/320#issuecomment-4618022490

   Happy to help in this space.  I benchmark/eval both coding harness agents 
and SDK agents and kiro-cli (and previously q-cli) are ones we use extensively 
and have access to.  
   
   Some easy tricks to get progressive disclosure are using a `skills` folder 
as the actual source for all skills and creating symlinks for the different 
vendor specific hidden folders such as `.kiro` , `.claude`, like so:
   
   ```                                                                          
                                                                            
   my-project/                                                                  
                                                                            
   ├── skills/                     # Canonical source                           
                                                                            
   │   ├── my-skill/                                                            
                                                                            
   │   │   └── SKILL.md                                                         
                                                                            
   │   └── another-skill/                                                       
                                                                            
   │       └── SKILL.md                                                         
                                                                            
   ├── .claude/                                                                 
                                                                            
   │   └── skills -> ../skills     # Symlink                                    
                                                                            
   ├── .kiro/                                                                   
                                                                            
   │   └── skills -> ../skills     # Symlink                                    
                                                                            
   └── ...                                                                      
                                                                            
   ```
   
   Unfortunately, the permission syntax is not compatible across products and 
has high variance in terms of approaches with other coding harnesses.  When 
searching this some time ago I generated this table:
                                                                                
                                                                                
                                                  
   | Aspect | Claude Code | kiro-cli |                                          
                                                                            
   |--------|-------------|----------|                                          
                                                                            
   | Config file | `.claude/settings.local.json` | `.kiro/agents/<name>.json` | 
                                                                            
   | Scope | Per-repo or global | Per-agent or CLI flag |                       
                                                                            
   | Syntax | `"Write(path/glob)"` | `"toolsSettings.write.allowedPaths": 
["glob"]` |                                                                     
  
   | Tool naming | PascalCase (`Write`, `Edit`, `Bash`) | lowercase (`write`, 
`read`, `grep`) |                                                             
   | Path style | Absolute or `~` expansion | Relative to CWD |                 
                                                                            
   | Granularity | Per-tool + per-path in one string | Separate `allowedTools` 
list + nested path config |         
   
   Particularly, kiro-cli  (2.5.1) [doesn't implement 
allowed-tools](https://github.com/kirodotdev/Kiro/issues/6055#issuecomment-4008428914)
 (not required in the 
[spec](https://agentskills.io/specification#allowed-tools-field) and 
experimental) at this stage.
   
   We can create its own 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to