Scanned skills

forcedotcom/sf-skills service-agentforce-channel-configure

Checked the catalogued skill at service-agentforce-channel-configure.

SkillTrust corpus scan 19 September 2026 v0.10.0 via skillsh Verify on GitHub
C AI-triaged 3
C Security

C; retained sample includes a medium finding · SD-008 · what this rule accepts as a false positive →

A Permissions

A set by no findings on this axis

B Transparency

B; retained sample includes a medium finding · SD-007 · what this rule accepts as a false positive →

3 findings
securitymedium SD-008
SKILL.md
securitymedium SD-008
assets/BotEmailDefinition.botEmailDefinition-meta.xml
transparencymedium SD-007
assets/mdapi-package.xml
17 suppressed by AI triage
transparencymedium SD-007 benign_example
assets/BotEmailDefinition.botEmailDefinition-meta.xml

The referenced endpoint is Salesforce's own SOAP API, a legitimate internal service.

transparencymedium SD-007 benign_example
assets/email/unfiled$public/AgentforceForServiceEmailTemplate.email-meta.xml

The endpoint is a Salesforce metadata namespace reference, not an executed outbound call.

transparencymedium SD-007 benign_example
assets/settings-mdapi-package.xml

The entry merely declares the Salesforce Metadata API endpoint for package deployment, not an active outbound call or permission grant.

securitymedium SD-008 benign_example
references/botemaildefinition.md

The file is a documentation snippet with no executable code; the flagged base64 string is likely part of documentation or absent in this context.

securitymedium SD-008 benign_example
references/channel-branch-email.md

The base64 string is part of a documentation example, not code that executes it.

securitymedium SD-008 benign_example
references/channel-branch-email.md

Base64 content is shown as part of documentation, not executed.

securitymedium SD-008 benign_example
references/channel-branch-email.md

The flagged base64 likely represents an embedded template snippet in docs.

securitymedium SD-008 benign_example
references/channel-branch-email.md

Same as above; documentation context, no execution.

securitymedium SD-008 benign_example
references/channel-branch-email.md

Base64 string appears in a descriptive section of the file.

permission_hygienehigh SD-003 benign_example
references/channel-branch-email.md

Absolute path is used for temporary build directories, not to escape sandbox.

permission_hygienehigh SD-003 benign_example
references/channel-branch-email.md

Path refers to a temporary working directory inside the project.

permission_hygienehigh SD-003 benign_example
references/channel-branch-email.md

Same temporary path usage as previous findings.

securitymedium SD-008 benign_example
references/channel-branch-email.md

Base64 content is part of documentation, not executed.

securitymedium SD-008 benign_example
references/channel-branch-email.md

Base64 string appears in a comment block describing XML templates.

permission_hygienehigh SD-003 benign_example
references/channel-branch-email.md

Temporary directory path used for package generation, not malicious.

securityhigh SD-007 benign_example
scripts/validate-botemaildefinition.py

Static XML namespace string, not an outbound network call or permission grant

securityhigh SD-007 benign_example
scripts/validate-emailtemplate.py

The URL is only used as an XML namespace string for parsing, not an outbound network request.