systematic debugging
A structured investigation workflow for a failing build, unexpected application behavior or a regression that keeps returning.
Repository star change: +587 over 24.12 hours. 2026-11-02
A Salesforce query-design workflow that separates SOQL or SOSL authoring from execution and bulk data operations.
Editorial review checked 2026-11-01 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
The source first establishes objects, required fields, filters and intended use, then chooses a relationship, aggregate or search shape. It directs execution and broader Apex work to other skills. Reference files and examples expand syntax, selectivity, security expectations and selector patterns.
Salesforce developers preparing a query or reviewing one for unnecessary fields, awkward relationship traversal or avoidable application-side filtering. It is a focused authoring aid rather than a substitute for org-specific schema and permission information.
A plausible query may fail against a particular org or return data the calling user should not receive. Static recommendations and the source's own numeric score guide do not establish production performance. The bundle also describes a post-write validation script with live query-plan behavior; inspect it and the target credentials separately. No Salesforce queries or hooks were executed for this review.
Unknown; inspect source requirements and supporting scripts.
First time installing a skill? Follow the walkthrough →
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
npx skills add https://github.com/forcedotcom/sf-skills/tree/a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e/skills/platform-soql-query --skill platform-soql-queryReview pinned skill folder ↗ · CLI documentation ↗
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
No configured text patterns matched. Unmatched or concealed behavior can still exist.
Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.
A temporary folder-copy check, not an agent installation or runtime safety verdict.
16 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.
Inventory SHA-256: f91f33f51ef02626f3d29ee99701e1f5ccc77afd1376c196f70a0f43e150b848
Local-reference warnings require review:
86/100 · Metadata coverage 100% · Model 1.0
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Bounded source inspection, not a runtime security audit. This inspection does not execute code.
1 text files inspected at this exact repository snapshot. 14 files outside the inspection budget or type allowlist. Dependencies were not installed or independently audited.
Absence of a pattern is not proof of safety. Permission needs and runtime behavior remain Unknown.
2c3dcb6711ff0add943cbfe14a2f038b84491949bd80ca88dda16329cf5a6052Confirm the target org and schema, write the smallest query that answers the question, inspect security and governor constraints, then validate in an authorized test environment. Keep bulk export and mutation tasks outside this authoring step.
Compare returned records and field access with expected fixtures, inspect the query plan where available and test representative data volumes. Successful parsing is weaker evidence than correct results under the intended user permissions.
Related by category; compare scope and dependencies before choosing an alternative.
A structured investigation workflow for a failing build, unexpected application behavior or a regression that keeps returning.
Repository star change: +587 over 24.12 hours. 2026-11-02
A Python UI reference for Gradio interfaces, component layouts, event handlers and interactive model demonstrations.
Repository star change: +9 over 24.12 hours. 2026-11-02
A project scaffold and bundling workflow for complex React-based HTML artifacts.
Repository star change: +478 over 24.12 hours. 2026-11-02
Explore agentforce architecture analyze as a development workflow from forcedotcom/sf-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +2 over 21.59 hours. 2026-11-02
Explore agentforce bot upgrade as a automation & agents workflow from forcedotcom/sf-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +2 over 21.59 hours. 2026-11-02
Explore agentforce d360 analyze as a development workflow from forcedotcom/sf-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Repository star change: +2 over 21.59 hours. 2026-11-02
Category-based discovery candidates. Inspect overlap, permissions and requirements; these combinations have not been integration-tested.
A multi-format plugin bundle that organizes planning, testing and implementation through reusable development skills and startup guidance.
A Claude Code review workflow for pull-request changes, with source references and separate local feedback and optional publication steps.
A Claude Code package for connecting Context7's hosted documentation lookup, useful when library versions matter to a coding task.
Category-based discovery candidates. Inspect overlap, permissions and requirements; these combinations have not been integration-tested.
Explore freellmpool as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore agents-party as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore Victauri as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.